When the TiDB cluster version is v6.1.5, an error occurs after reloading the entire cluster following the modification of the tidb_mem_quota_query parameter via the command line

Translated
1

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

Original topic: tidb集群版本为v6.1.5，命令行修改tidb_mem_quota_query参数后，reload整个集群就报错

| username: vcdog

[TiDB Usage Environment] Production Environment
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
The TiDB cluster version is v6.1.5. After modifying the tidb_mem_quota_query parameter via the command line and reloading the entire cluster, an error occurs:

 {ssh_stderr: , ssh_stdout: [2023/09/11 09:41:13.539 +08:00] [FATAL] [terror.go:292] ["unexpected error"] [error="config file /acdata/tidb-cluster/tidb-deploy/tidb-4000/conf/tidb.toml contained invalid configuration options: tidb_mem_quota_query; check TiDB manual to make sure this option has not been deprecated and removed from your TiDB version if the option does not appear to be a typo"]

Checking the configuration file on the tidb-server node shows two parameters:
mem-quota-query = 64424509440
tidb_mem_quota_query = 64424509440

Using the command tiup cluster edit-config tidb-cluster-name to re-edit the cluster configuration file, saving and exiting, and then reloading still results in an error:

image
image1380×580 519 KB

[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

image
image1446×370 14.9 KB

2
| username: TiDB_C罗 | Original post link

What is the method for the command line? Directly modify the configuration file manually, then use the edit-config method.

3
| username: vcdog | Original post link

tiup cluster edit-config tidb-cluster-name

4
| username: vcdog | Original post link

  1. The command executed in the command line is:
    mysql> set global tidb_mem_quota_query = 64424509440;

  2. After modifying and saving using edit-config, it prompts that the mem-quota-query and tidb_mem_quota_query parameters cannot coexist.

  3. Manually deleting mem-quota-query and tidb_mem_quota_query from the tidb-server configuration file and reloading still results in an error.

5
| username: 有猫万事足 | Original post link

In the complete configuration file example on GitHub, this parameter cannot be found.

Even the description of the 7.1 configuration file does not allow setting this parameter.

It should only be set through the client. However, once set, it should be persistent.

The reason for not modifying through the configuration file is probably because this parameter may be modified frequently, and after modifying the configuration file, a reload is required, which is obviously unacceptable for an online system.

6
| username: 像风一样的男子 | Original post link

The official website clearly states that in version 6.1, this parameter has been converted to a system variable and is no longer configured through the configuration file. The mem-quota-query parameter has also been removed.

image
image1110×358 18.5 KB

image
image1380×488 66.7 KB

7
| username: 大飞哥online | Original post link

Use the set method to change it.

8
| username: 胡杨树旁 | Original post link

Has version 6.1.5 been changed to use variables? Try using the “set global *****” method.

9
| username: zhanggame1 | Original post link

This parameter is persisted in TiKV and cannot be changed through the parameter file.

10
| username: system | Original post link

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