[FLINK-37278] Optimize regular schema evolution topology's performance #3912
+93
−123
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.
This closes FLINK-37278.
Currently, regular SE topology uses the following process to drain existing
DataChangeEvent
s in the pipeline:FlushEvent
to downstream.FlushSuccessEvent
notifications from Sink.As a result, all schema change requests will took at least 1 second to finish, after at least one polling interval.
This PR replaces the polling code with maintaining a pending schema change request queue, where SchemaCoordinator could manage all pending clients and effectively blocking them from handling upstream events. Schema evolution process could start immediately after
FlushSuccessEvent
got reported, needless to wait for polling requests from clients.With this change, time consumption of
testRegularTablesSourceInMultipleParallelism
test case has been reduced from ~6 minutes to ~50 seconds.