[Enhancement] Prepare/commit transaction stream load asynchronously #328
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.
What type of PR is this:
Which issues of this PR fixes :
Fixes #
For transaction stream load at at-least-once mode, only load phase is executed asynchronously in a thread pool whose size is controlled by
sink.io.thread-count
, but the prepare/commit phase is executed in the single thread used for schedule, and it can block the schedule thread if prepare/commit takes much time. For multiple tables case, this can prevent to schedule other tables to load/prepare/commit, and lead to performance issue. So we make the prepare/commit also asynchronous.Problem Summary(Required) :
Checklist: