Repository navigation
Conversation
VGalaxies
pushed a commit
to VGalaxies/iotdb
that referenced
this pull request
Oct 26, 2026
…#18948) * [Fix] Prevent stale schema queue closes from following leader transfers * [Pipe] Wait for historical transfer before asserting mods
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.
Schema listener cleanup uses the local DataNode's Pipe metadata. If the SchemaRegion leader steps down while a cleanup write is in flight, Ratis can forward that close to the new leader after it has opened the queue for a new task. The late close invalidates the active iterator and stalls schema replication.
Allow consensus requests to opt out of remote forwarding and apply this to schema queue closes. The new leader can reevaluate cleanup on its next metadata synchronization. Ordinary writes and queue opens retain their existing routing, and the serialized plan format is unchanged.
Validation:
origin/masterRatis implementation because it forwards the stale request (status 200 instead of 400).