Fix unstable test: handle MiniCluster shutdown gracefully in collect … #6913
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.
[flink] Fix unstable test: handle MiniCluster shutdown gracefully in collect method
Purpose
Linked issue: close #5563
This PR fixes the unstable test
PrimaryKeyFileStoreTableITCase.testNoChangelogProducerStreamingRandomby addressing a race condition in thecollectmethod. The timeout thread was attempting to cancel jobs after the MiniCluster had already shut down, causingIllegalStateExceptionand premature test termination. The fix follows the pattern used in Flink'sCollectResultFetcherto gracefully handle shutdown scenarios.Tests
PrimaryKeyFileStoreTableITCase.testNoChangelogProducerStreamingRandomwhich was failing intermittently with:IllegalStateException: MiniCluster is not yet running or has already been shut downThe fix ensures that:
getJobStatus()throws an exception (e.g., MiniCluster shutdown), we assume the job has terminated instead of attempting cancellationIllegalStateExceptiongracefullyAPI and Format
No API or storage format changes.
Documentation
No documentation changes needed. This is a test stability fix.