-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sink(ticdc): limit the number of transactions cached in a mysql worker (#10892) #10941
Merged
ti-chi-bot
merged 1 commit into
pingcap:release-7.5
from
ti-chi-bot:cherry-pick-10892-to-release-7.5
May 20, 2024
Merged
sink(ticdc): limit the number of transactions cached in a mysql worker (#10892) #10941
ti-chi-bot
merged 1 commit into
pingcap:release-7.5
from
ti-chi-bot:cherry-pick-10892-to-release-7.5
May 20, 2024
Conversation
This file contains 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
ti-chi-bot
added
lgtm
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
type/cherry-pick-for-release-7.5
This PR is cherry-picked to release-7.5 from a source PR.
labels
Apr 22, 2024
ti-chi-bot
added
the
cherry-pick-approved
Cherry pick PR approved by release team.
label
Apr 22, 2024
CharlesCheung96
force-pushed
the
cherry-pick-10892-to-release-7.5
branch
from
April 26, 2024 09:17
77a3200
to
445a471
Compare
CharlesCheung96
force-pushed
the
cherry-pick-10892-to-release-7.5
branch
from
April 26, 2024 10:19
445a471
to
c68c96e
Compare
/retest |
CharlesCheung96
approved these changes
Apr 28, 2024
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CharlesCheung96 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
3 similar comments
/retest |
/retest |
/retest |
CharlesCheung96
added a commit
to CharlesCheung96/tiflow
that referenced
this pull request
Jun 6, 2024
…ql worker (pingcap#10892) (pingcap#10941)" This reverts commit 764fdb4.
This was referenced Jun 6, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
cherry-pick-approved
Cherry pick PR approved by release team.
lgtm
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
type/cherry-pick-for-release-7.5
This PR is cherry-picked to release-7.5 from a source PR.
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 is an automated cherry-pick of #10892
What problem does this PR solve?
Issue Number: close #10896
What is changed and how it works?
Txn.Worker
to reduce interdependencies between modules.Txn.Worker
.causality.worker
that support different batch control policies.Check List
Tests
In the workload skew case, the maximum performance improvement after optimization is about 300% ~ 1000%.
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note