-
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
*: move config file option mem-quota-query to sysvar #34141
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. |
Please review @morgo |
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/f1fdc4775c5ec02828fefe7ba17c42184a0a66dc |
@espresso98 Please fix the conflict. |
… IndexLookup, Proj and Sel (pingcap#34091) ref pingcap#33945
…rs halfway (pingcap#34165) ref pingcap#32306, close pingcap#34164
close pingcap#31954, close pingcap#33014, close pingcap#33832
c257548
to
37dcc42
Compare
/merge |
This pull request has been accepted and is ready to merge. Commit hash: f1fdc47
|
TiDB MergeCI notify✅ Well Done! New fixed [1] after this pr merged.
|
What problem does this PR solve?
Issue Number: ref #33769
Problem Summary:
The option
mem-quota-query
has historically been a config option andtidb-mem-quota-query
already exists as the only session variable. Based on requirements from cloud & PM it should instead be aGLOBAL
sysvar.What is changed and how it works?
This does the minimum work to convert
mem-quota-query
to a global (cluster-wide) sysvar, and removes the config option (placing it in the previously deprecated list).Check List
Tests
The previous default (TiDB 2.1, 3.1) for memory quota was 32G. When upgrading from TiDB 2.1/3.0 to 4.0 the 32G limit is preserved in upgrade, so I was concerned that this might create an upgrade problem for some users.
However, if you manually try an upgrade from v2.1/3.0 -> 4.0 -> 5.0, the 32G default is lost and 1G is used. So the intended compatibility feature is not working correctly. This is why the test
TestIssue20900_1
was removed -- it does not work past version 4.0 any more. Because thedefault_memory_quota_query
is deleted frommysql.tidb
it is also not possible to fix this in a new bootstrap task. The new default is always picked up.Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.