Repository navigation
lastSequenceNr should reflect the snapshot sequence - #27993
Merged
Merged
Conversation
…h 0 when journal is empty (#27496) * lastSequenceNr should reflect the snapshot sequence number and not start at 0 when there was no journal to begin with. * Use LevelDBJournal in Test Case The test case now properly simulates a recovery from a snapshot without a journal. (cherry picked from commit df2a1d8)
akka-ci
added
validating
|
Test PASSed. |
Contributor
Author
|
merging since it's a cherry pick from other PR that has been reviewed, I'll follow up with the additional things mention in other pr |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Forward port of #27496
(cherry picked from commit df2a1d8)