-
Notifications
You must be signed in to change notification settings - Fork 283
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
sorter(cdc): add config cache-size (#9024) #9030
sorter(cdc): add config cache-size (#9024) #9030
Conversation
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
d3249aa
to
e4070dd
Compare
ref pingcap#8974 Signed-off-by: qupeng <qupeng@pingcap.com>
e4070dd
to
4a1a13a
Compare
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 45a4263
|
…ot/ticdc into cherry-pick-9024-to-release-6.5
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 684b61e
|
/merge |
This pull request has been accepted and is ready to merge. Commit hash: b781830
|
This is an automated cherry-pick of #9024
What problem does this PR solve?
Issue Number: ref #8974
What is changed and how it works?
#8982 sets
sorter.max-memory-percentage
to0
by default. It can cause an error:So we add a new config
sorter.cache-size
. The dafault value is128
, which means128M
.Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note