Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[IMPROVED] High CPU and Memory usage on replicated mirrors with very high starting sequence. #4249

Merged
merged 1 commit into from Jun 16, 2023
Merged

[IMPROVED] High CPU and Memory usage on replicated mirrors with very high starting sequence. #4249

merged 1 commit into from Jun 16, 2023

Commits on Jun 16, 2023

  1. When creating replicated mirrors where the source stream had a very l… 

    …arge starting sequence number, the server would use excessive CPU and Memory.

This is due to the mirroring functionality trying to skip messages when it detects a gap. In a replicated stream this puts excessive stress on the raft system.
This step is not needed at all if the mirror stream has no messages, we can simply jump ahead.

Signed-off-by: Derek Collison <derek@nats.io>
    @derekcollison
    derekcollison committed Jun 16, 2023
    Configuration menu
    Copy the full SHA
    087a28a View commit details
    Browse the repository at this point in the history