Repository navigation
Conversation
* Fix Pipe leader-change procedure ordering * Fix procedure recovery during leader startup * Fix leader readiness after procedure workers start * Fix internal procedure recovery readiness (cherry picked from commit 727b83a)
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.
Summary
Backports correctness fixes from #17821 and #19318 to
dev/1.3.Scenario
During ConfigNode startup or a leader change, required node heartbeat samples may still be arriving while Pipe-related procedures need recovery. Warm-up can be delayed by unrelated region or consensus samples, or recovery work can run before Pipe leader-change state is restored. This can delay service or allow work to proceed against incomplete leader state.
Expected behavior
The leader becomes externally ready only after the required warm-up and Pipe recovery ordering is satisfied. Internal recovery procedures retain their dedicated readiness path.
Validation
mvn -T 1 clean test -pl iotdb-core/confignode -am -Dtest=ConfigRegionStateMachineTest,LoadManagerTest -Dsurefire.failIfNoSpecifiedTests=false