SET tidb_mem_quota_query = 8 << 30; Not Effective Show Config Where Name Like '%mem_quota_query%'

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: SET tidb_mem_quota_query = 8 << 30; 不生效 show config where name like ‘%mem_quota_query%’

| username: xiaoxiaozuofang

【TiDB Usage Environment】Production Environment / Testing / PoC
【TiDB Version】
【Reproduction Path】What operations were performed when the issue occurred
【Encountered Issue: SET tidb_mem_quota_query = 8 << 30; not effective, show config where name like ‘%mem_quota_query%’】
【Resource Configuration】
【Attachments: Screenshots/Logs/Monitoring】

2
| username: 裤衩儿飞上天 | Original post link

tidb_mem_quota_query is a system variable, right? Try using show variables like ‘%XXXXXXXX%’ to check.

3
| username: 裤衩儿飞上天 | Original post link

You can refer to System Variables | PingCAP Documentation Center

4
| username: TiDBer_pkQ5q1l0 | Original post link

set global tidb_mem_quota_query = xxx

5
| username: ljluestc | Original post link

Verify that you are running the command as the TiDB user and have the necessary permissions.
Check if the value of tidb_mem_quota_query is set in the configuration file (e.g., tidb.toml) and is not being overridden by any other configuration files.
Try setting the memory quota using TiDB Dashboard or TiDB Lightning to see if it takes effect.
Restart the TiDB service to see if it takes effect.
If the above steps do not resolve the issue, you can provide more details about your TiDB usage environment, version, and replication path. Additionally, you can share any error messages or logs related to the issue to help with troubleshooting.

6
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.