[Pipe] Fix config event race in idempotent table IT - #18403
Merged
jt2594838 merged 1 commit intoAug 5, 2026
Conversation
jt2594838
approved these changes
Aug 5, 2026
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
2 participants
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
IoTDBPipeIdempotentITexecutes preparation statements on the sender and immediately executes the conflict statement on the receiver. Since Pipe transfers config events asynchronously, the receiver may not have the required table or user yet, causing flakydoes not existerrors before the idempotent conflict is created.This change adds a database config event as a progress marker after the preparation statements and waits until it reaches the receiver. It also updates the final database count to include the marker database.
Tests
mvn spotless:apply -pl integration-test -Pwith-integration-teststestTableAlterUserIdempotent3testSetTableColumnCommentIdempotentIoTDBPipeIdempotentIT: 23 methods passed; one method hit a transient DataNodeConnection refusederror and passed when rerun separately.