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] Do not load blocks when calling LoadNextMsg for the first time after restart or long inactivity #4969

Merged
merged 1 commit into from
Jan 18, 2024
Merged

[IMPROVED] Do not load blocks when calling LoadNextMsg for the first time after restart or long inactivity #4969

merged 1 commit into from
Jan 18, 2024

Commits on Jan 18, 2024

  1. When calling LoadNextMsg for the first time, the starting sequence wi… 

    …ll be at the beginning of the stream. We would walk all blocks, which if fss was loaded we could skip fairly quickly. However on a restart this could cause memory blocks to be loaded in just to be skipped.

Signed-off-by: Derek Collison <derek@nats.io>
    @derekcollison
    derekcollison committed Jan 18, 2024
    Configuration menu
    Copy the full SHA
    b4b1f91 View commit details
    Browse the repository at this point in the history