Skip to content
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

Merged
merged 2 commits into from
Mar 26, 2020

Conversation

zimulala
Copy link
Contributor

@zimulala zimulala commented Mar 26, 2020

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

Check List

Tests

  • Unit test

Release note

@zimulala zimulala added type/enhancement The issue or PR belongs to an enhancement. component/server labels Mar 26, 2020
@zimulala
Copy link
Contributor Author

PTAL @jackysp

@jackysp jackysp requested a review from coocood March 26, 2020 08:28
Copy link
Member

@jackysp jackysp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jackysp jackysp added the status/LGT1 Indicates that a PR has LGTM 1. label Mar 26, 2020
@coocood
Copy link
Member

coocood commented Mar 26, 2020

LGTM

@codecov
Copy link

codecov bot commented Mar 26, 2020

Codecov Report

Merging #15726 into master will not change coverage by %.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #15726   +/-   ##
===========================================
  Coverage   80.4092%   80.4092%           
===========================================
  Files           504        504           
  Lines        134967     134967           
===========================================
  Hits         108526     108526           
  Misses        17965      17965           
  Partials       8476       8476           

Copy link
Contributor

@AilinKid AilinKid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zimulala zimulala added status/can-merge Indicates a PR has been approved by a committer. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Mar 26, 2020
@sre-bot
Copy link
Contributor

sre-bot commented Mar 26, 2020

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Mar 26, 2020

@zimulala merge failed.

@zimulala
Copy link
Contributor Author

/run-all-tests

@zimulala
Copy link
Contributor Author

/run-integration-common-test
/run-unit-test

@jackysp
Copy link
Member

jackysp commented Mar 26, 2020

/merge

@sre-bot
Copy link
Contributor

sre-bot commented Mar 26, 2020

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Mar 26, 2020

@zimulala merge failed.

@zimulala
Copy link
Contributor Author

/run-check_dev_2
/run-common-test

@sre-bot
Copy link
Contributor

sre-bot commented Mar 26, 2020

cherry pick to release-4.0 in PR #15730

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/config component/server status/can-merge Indicates a PR has been approved by a committer. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants