[FIXED] R1 stream move would sometimes lose all msgs. #4413
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
…e replica peer has not registered a catchup request. This would cause us to think the replica was caughtup incorrectly and drop our leadership, which would cancel any cacthup requests. Signed-off-by: Derek Collison <derek@nats.io>
wallyqs
approved these changes
Aug 22, 2023
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 moving streams, we could check too soon and be in a gap where the replica peer has not registered a catchup request but had made contact via the NRG layer.
This would cause us to think the replica was caught up, incorrectly, and drop our leadership, which would cancel any catchup requests.
Signed-off-by: Derek Collison derek@nats.io