After modifying the configuration information in topology.yaml, the configuration does not take effect after restarting with tiup cluster restart $cluster_name

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

Original topic: 修改topology.yaml的配置信息后,tiup cluster restart $cluster_name重启后,配置不生效

| username: grafanab

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]
After modifying the configuration information in topology.yaml and restarting with tiup cluster restart $cluster_name, the configuration does not take effect.
Example:
tikv:
memory-usage-limit: 10G
storage.block-cache.capacity: 8G
After modifying the memory usage, restarting TiDB does not take effect. Is there any way to make the configuration file take effect?

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

tiup cluster edit-config xxx is used to modify the configuration of an already installed cluster; modifying topology.yaml is no longer effective.

| username: 普罗米修斯 | Original post link

You need to edit the cluster edit-config and then reload the corresponding nodes.

| username: caiyfc | Original post link

The topology.yaml file is only used during the initial deployment. After the deployment is complete, this file is no longer needed. At this point, to modify cluster parameters, you need to use the command tiup cluster edit-config $cluster_name. After making the modifications, follow the prompts to reload the corresponding components or nodes. The restart command only restarts and does not apply the configuration, while the reload command will apply the configuration.

| username: zhanggame1 | Original post link

Refer to the official documentation
TiUP Common Maintenance Operations | PingCAP Documentation Center

| username: TiDBer_小阿飞 | Original post link

edit-config

| username: andone | Original post link

You need to use tiup reload. Restarting will not take effect.

| username: Kongdom | Original post link

Restart only restarts the node.
Reload fetches the modified configuration information from TiUP, loads it, and then restarts the node.

Restart does not fetch the modified configuration information, so it does not take effect.

| username: dba远航 | Original post link

Use tiup cluster edit-config xxx to modify the configuration of an already installed cluster.

| username: grafanab | Original post link

First, modify the configuration file, then execute tiup cluster edit-config <cluster>, and finally execute tiup cluster reload?

| username: Miracle | Original post link

To modify the configuration file, use tiup cluster edit-config xxxx, and then reload.

| username: heiwandou | Original post link

tiup cluster edit-config or adjust online

| username: caiyfc | Original post link

If the cluster has already been deployed, you can directly use tiup cluster edit-config <cluster-name>, which will allow you to access the configuration file. After making the changes, you will be prompted to reload. You can then use tiup cluster reload <cluster-name> to apply the changes.

| username: 随缘天空 | Original post link

You can use the edit-config command to modify and then reload, or you can modify it online.
Here is the link: tiup cluster edit-config | PingCAP 文档中心
在线修改集群配置 | PingCAP 文档中心

| username: TIDB-Learner | Original post link

Reload

| username: system | Original post link

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