Fix unstable testListRebalanceProgress testcase #2386
+43
−6
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.
Purpose
Linked issue: close #2372
Brief change log
Fix the unstable testListRebalanceProgress testcase that was previously failing,
Issue
FlinkProcedureITCase used to creates 10 tables rapidly while server 3 is marked
PERMANENT_OFFLINE, causing all replicas to concentrate on servers 0, 1, and 2. This creates high load that can exceed the current 60-second timeout forwaitUntilTableReady(). The test fails intermittently with replicas showingNoneReplicastate instead of the expectedOnlineReplicastate.Fix
waitUntilTableReady()timeout configurable (allowing tests to specify longer timeouts)Tests
FlinkProcedureITCase.java has been fixed.