-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
variables: Increase default innodb_buffer_pool_size to 4GiB #57460
variables: Increase default innodb_buffer_pool_size to 4GiB #57460
Conversation
Signed-off-by: Xiaoguang Sun <[email protected]>
Hi @sunxiaoguang. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. 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 kubernetes-sigs/prow repository. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #57460 +/- ##
================================================
+ Coverage 72.8488% 73.5994% +0.7505%
================================================
Files 1672 1672
Lines 462666 464751 +2085
================================================
+ Hits 337047 342054 +5007
+ Misses 104821 101916 -2905
+ Partials 20798 20781 -17
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dveeden, hawkingrei 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 |
[LGTM Timeline notifier]Timeline:
|
/ok-to-test |
/retest |
What problem does this PR solve?
Issue Number: close #57459
Problem Summary: Some applications are complaining that the innodb_buffer_pool_size is too small. Since it doesn't affect any logic in TiDB, we can safely increase the default value so it will work out of box in this situation
What changed and how does it work?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.