From 3399aa151e32c963ac4d8428936dc8cec4d80c04 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Thu, 23 Jan 2025 11:11:53 +0800 Subject: [PATCH] tiup: fix tiproxy data_dir (#20119) (#20128) --- config-templates/simple-tiproxy.yaml | 2 -- tiup/tiup-cluster-topology-reference.md | 3 --- 2 files changed, 5 deletions(-) diff --git a/config-templates/simple-tiproxy.yaml b/config-templates/simple-tiproxy.yaml index e05afa98762a1..d70b096de1165 100644 --- a/config-templates/simple-tiproxy.yaml +++ b/config-templates/simple-tiproxy.yaml @@ -33,14 +33,12 @@ tikv_servers: tiproxy_servers: - host: 10.0.1.11 deploy_dir: "/tiproxy-deploy" - data_dir: "/tiproxy-data" port: 6000 status_port: 3080 config: labels: { zone: "east" } - host: 10.0.1.12 deploy_dir: "/tiproxy-deploy" - data_dir: "/tiproxy-data" port: 6000 status_port: 3080 config: diff --git a/tiup/tiup-cluster-topology-reference.md b/tiup/tiup-cluster-topology-reference.md index d57df126435c8..64ea2b63e9500 100644 --- a/tiup/tiup-cluster-topology-reference.md +++ b/tiup/tiup-cluster-topology-reference.md @@ -439,8 +439,6 @@ tiflash_servers: - `deploy_dir`: Specifies the deployment directory. If it is not specified or specified as a relative directory, the directory is generated based on the `deploy_dir` directory configured in `global`. -- `data_dir`: Specifies the data directory. If it is not specified or specified as a relative directory, the directory is generated based on the `data_dir` directory configured in `global`. - - `numa_node`: Allocates the NUMA policy to the instance. Before specifying this field, you need to make sure that the target machine has [numactl](https://linux.die.net/man/8/numactl) installed. If this field is specified, cpubind and membind policies are allocated using [numactl](https://linux.die.net/man/8/numactl). This field is of string type. The value is the ID of the NUMA node, such as `"0,1"`. - `config`: The configuration rule of this field is the same as the `tiproxy` configuration rule in `server_configs`. If this field is configured, the field content is merged with the `tiproxy` content in `server_configs`. If these two fields overlap, the content of this field takes effect. Subsequently, a configuration file is generated and sent to the machine specified in `host`. @@ -454,7 +452,6 @@ Among the above fields, you cannot modify the following configured fields after - `host` - `port` - `deploy_dir` -- `data_dir` - `arch` - `os`