-
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
"advanced" memory quota variables have no effect #32286
Comments
This is an easy fix if this is true: we have a feature called "remove sysvars" now: #28931 @yudongusa Can you confirm that we can remove these variables from tidb master? |
I'll leave this for @XuHuaiyu to double check as this is cap memory usage of hash join operator. |
4th issue: #32289 |
I just rememebered I have a related PR on this: #30848 -- The following system variables are 'known' to not be working correctly: TiDBMemQuotaQuery, TiDBMemQuotaHashJoin, TiDBMemQuotaMergeJoin, TiDBMemQuotaSort, TiDBMemQuotaTopn, TiDBMemQuotaIndexLookupReader. So it makes sense they should just be removed. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
set tidb_mem_quota_hashjoin=0;
2. What did you expect to see? (Required)
This variable is "deprecated". A deprecated variable should still have some effect, especially since the documentation still claims that they have some effect: https://docs.pingcap.com/tidb/dev/configure-memory-usage
3. What did you see instead (Required)
These variables should be removed from the documentation if they have no effect.
The source code claims that these variables "do not take any effect anymore", and there's even a TODO to remove them in 4.1. This warning has been in the code for nearly 2 years. Maybe finally time to remove these entirely?
https://github.com/pingcap/tidb/blob/master/sessionctx/variable/session.go#L1904
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: