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

[FIXED] Improvements to dealing with old or non-existant index.db #5893

Merged
merged 1 commit into from
Sep 17, 2024
Merged

[FIXED] Improvements to dealing with old or non-existant index.db #5893

merged 1 commit into from
Sep 17, 2024

Commits on Sep 16, 2024

  1. Improvements to dealing with old or non-existant index.db files durin… 

    …g snapshot restore or restart.

We had a condition where an old index.db was not able to properly restore a stream due to max msgs per subject being set and certain blocks being compacted away and removing subject info for those sequences.
In addition we fixed recovery after Truncate and PurgeEx by subject when the index.db was corrupt or not available.

This change also moves generating the index.db file to after writing the blocks during a snapshot and we do a force call to make sure it is written even when complex.

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