Repository navigation
Conversation
Collaborator
Author
Review summary
|
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
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.
Description
During peer recovery, rebuilding a peer can overlap server startup and dispatcher progress-index updates, leaving recovery notifications stale. This change coordinates peer reconstruction, startup, and watermark/index publication, and cleans up partially initialized server state when startup fails so a retry can rebuild consistently. Recovery regression tests cover the rebuilt-peer path.
Validation
IoTDBConsensusSubscriptionRecoveryTableIT.testRebuiltConsumersResumeAfterFullClusterRestartfailed after restart: the test observed only the initial 16 rows and not the 64 rows written before restart. The cause and relationship to this change are unconfirmed.