-
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
config: remove per-table-memory-quota min value check #3022
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
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. |
Remove per-table-memory-quota min value check, because it is possible to capture thousands of tables, and in this case, 6MB is too large. Also, it changes the default quota from 20MB to 10MB. Tests show that no obvious bottleneck for 10MB. Signed-off-by: Neil Shen <overvenus@gmail.com>
541e9e1
to
eecd4c9
Compare
@@ -117,5 +117,5 @@ func TestServerConfigValidateAndAdjust(t *testing.T) { | |||
require.Regexp(t, ".*does not contain a port", conf.ValidateAndAdjust()) | |||
conf.AdvertiseAddr = "advertise:1234" | |||
conf.PerTableMemoryQuota = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can add a test, when conf.PerTableMemoryQuota
is zero, ValidateAndAdjust
will reset it to default quota
Signed-off-by: Neil Shen <overvenus@gmail.com>
We should probably discuss which branches this PR needs to be cherry-picked to. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 9982e2a
|
/run-integration-tests |
/run-kafka-tests |
1 similar comment
/run-kafka-tests |
@overvenus: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/run-kafka-tests |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #3037. |
In response to a cherrypick label: new pull request created: #3038. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #3039. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #3040. |
What problem does this PR solve?
Remove per-table-memory-quota min value check, because it is
possible to capture thousands of tables, and in this case, 6MB is
too large.
Also, it changes the default quota from 20MB to 10MB. Tests show
that no obvious bottleneck for 10MB.
Cc https://github.com/pingcap/ticdc/pull/2561
Metrics: https://gist.github.com/overvenus/183013d6b68c73f6b31d0dc1e5fb2bec
Check List
Tests
See above.
Related changes
Release note