-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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, server: change the default value of max-server-connections #15726
Conversation
PTAL @jackysp |
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.
LGTM
LGTM |
Codecov Report
@@ Coverage Diff @@
## master #15726 +/- ##
===========================================
Coverage 80.4092% 80.4092%
===========================================
Files 504 504
Lines 134967 134967
===========================================
Hits 108526 108526
Misses 17965 17965
Partials 8476 8476 |
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.
LGTM
/run-all-tests |
@zimulala merge failed. |
/run-all-tests |
/run-integration-common-test |
/merge |
/run-all-tests |
@zimulala merge failed. |
/run-check_dev_2 |
cherry pick to release-4.0 in PR #15730 |
What problem does this PR solve?
Problem Summary:
max-server-connections
is added in #14409, and some users may think this value is too small.What is changed and how it works?
What's Changed:
Change the default value of max-server-connections to 0, and if the value is 0, the number of connections is unlimited.
Related changes
pingcap/docs
/pingcap/docs-cn
: reference: updatemax-server-connections
docs-cn#2574pingcap/tidb-ansible
:Check List
Tests
Release note