[FIXED] Filestore initial first seq purge after restart #6753
Conversation
This file contains 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
Signed-off-by: Maurice van Veen <[email protected]>
MauriceVanVeen
force-pushed
the
maurice/fs-init-fseq
branch
from
7734860 to
48b8744
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When creating a stream a custom first sequence can be used to skip ahead the initial stream sequence. However, if a file-based stream was setup to use a custom first sequence, if the server restarted it could come up without any messages. Essentially fully purging the stream of its contents.
This would only happen IFF:
This bug exists in all versions starting from 2.10.0, until this fix is released. It can be mitigated prior to a restart by ensuring streams that apply above conditions have had the first message at that sequence removed.
Signed-off-by: Maurice van Veen [email protected]