[IOTDB-6194] Remove _list from parameter target_config_node_list

src/UserGuide/Master/Deployment-and-Maintenance/Docker-Install.md

@@ -38,12 +38,12 @@ docker run -d --name iotdb-service \
               --ip 172.18.0.6 \
               -p 6667:6667 \
               -e cn_internal_address=iotdb-service \
-              -e cn_target_config_node_list=iotdb-service:10710 \
+              -e cn_target_config_node=iotdb-service:10710 \
               -e cn_internal_port=10710 \
               -e cn_consensus_port=10720 \
               -e dn_rpc_address=iotdb-service \
               -e dn_internal_address=iotdb-service \
-              -e dn_target_config_node_list=iotdb-service:10710 \
+              -e dn_target_config_node=iotdb-service:10710 \
               -e dn_mpp_data_exchange_port=10740 \
               -e dn_schema_region_consensus_port=10750 \
               -e dn_data_region_consensus_port=10760 \
@@ -76,14 +76,14 @@ services:
       - cn_internal_address=iotdb-service
       - cn_internal_port=10710
       - cn_consensus_port=10720
-      - cn_target_config_node_list=iotdb-service:10710
+      - cn_target_config_node=iotdb-service:10710
       - dn_rpc_address=iotdb-service
       - dn_internal_address=iotdb-service
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
       - dn_schema_region_consensus_port=10750
       - dn_data_region_consensus_port=10760
-      - dn_target_config_node_list=iotdb-service:10710
+      - dn_target_config_node=iotdb-service:10710
     volumes:
         - ./data:/iotdb/data
         - ./logs:/iotdb/logs
@@ -112,7 +112,7 @@ services:
     container_name: iotdb-confignode
     environment:
       - cn_internal_address=iotdb-2
-      - cn_target_config_node_list=iotdb-1:10710
+      - cn_target_config_node=iotdb-1:10710
       - cn_internal_port=10710
       - cn_consensus_port=10720
       - schema_replication_factor=3
@@ -132,7 +132,7 @@ services:
     environment:
       - dn_rpc_address=iotdb-2
       - dn_internal_address=iotdb-2
-      - dn_target_config_node_list=iotdb-1:10710
+      - dn_target_config_node=iotdb-1:10710
       - data_replication_factor=3
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
@@ -151,7 +151,7 @@ services:
 
 Notice：
 
-1. The `dn_target_config_node_list` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
+1. The `dn_target_config_node` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
 2. In this docker-compose file，`iotdb-2` should be replace with the real IP or hostname of each node to generate docker compose files in the other nodes.
 3. The services would talk with each other, so they need map the /etc/hosts file or add the `extra_hosts` to the docker compose file.
 4. We must start the IoTDB services of `iotdb-1` first at the first time of starting.

src/UserGuide/Master/QuickStart/ClusterQuickStart.md

@@ -84,7 +84,7 @@ It's recommended that the configurations of iotdb-common.properties and the heap
 Before starting the IoTDB cluster, make sure the configurations are correct and there is no any data in the working directory. 
 
 #### 1.3.1. start the first node
-That is `cn_target_config_node_list` in above configuration table.
+That is `cn_target_config_node` in above configuration table.
 Execute these commands below in node of `192.168.132.10`.
 ```shell
 cd /data/iotdb
@@ -99,7 +99,7 @@ tail -f logs/log_datanode_all.log
 If there is no such logs mentioned abolve or there are some `Exception`s in log files, it's failed. Then please check `log_confignode_all.log` and `log_datanode_all.log` in directory of `/data/iotdb/logs`.
 
 **Notice**：
-- Make sure the first node, especially the first ConfigNode that `cn_target_config_node_list` specified, starting successfully, and then start the other services.
+- Make sure the first node, especially the first ConfigNode that `cn_target_config_node` specified, starting successfully, and then start the other services.
 - If starting failed，it's necessary to do [cleanup](#【reference】cleanup) before starting again.
 - How to start service ConfigNode or DataNode alone: 
 ```shell
@@ -173,7 +173,7 @@ It's the same as starting the other nodes mentioned above. That is downloading I
 **Notice**
 - It's must be cleaned up, in other words doing [cleanup](#cleanup) in it.
 - `cluster_name` of `iotdb-common.properties` must be the same to the cluster.
-- `cn_target_config_node_list` and `dn_target_config_node_list` must be the same to the cluster.
+- `cn_target_config_node` and `dn_target_config_node` must be the same to the cluster.
 - The old data wouldn't be moved to the new node but the new data would be.
 
 ### 2.1. configuration

src/UserGuide/Master/stage/Cluster/Get-Installation-Package.md

@@ -103,12 +103,12 @@ docker run -d --name iotdb-service \
               --ip 172.18.0.6 \
               -p 6667:6667 \
               -e cn_internal_address=iotdb-service \
-              -e cn_target_config_node_list=iotdb-service:10710 \
+              -e cn_target_config_node=iotdb-service:10710 \
               -e cn_internal_port=10710 \
               -e cn_consensus_port=10720 \
               -e dn_rpc_address=iotdb-service \
               -e dn_internal_address=iotdb-service \
-              -e dn_target_config_node_list=iotdb-service:10710 \
+              -e dn_target_config_node=iotdb-service:10710 \
               -e dn_mpp_data_exchange_port=10740 \
               -e dn_schema_region_consensus_port=10750 \
               -e dn_data_region_consensus_port=10760 \
@@ -141,14 +141,14 @@ services:
       - cn_internal_address=iotdb-service
       - cn_internal_port=10710
       - cn_consensus_port=10720
-      - cn_target_config_node_list=iotdb-service:10710
+      - cn_target_config_node=iotdb-service:10710
       - dn_rpc_address=iotdb-service
       - dn_internal_address=iotdb-service
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
       - dn_schema_region_consensus_port=10750
       - dn_data_region_consensus_port=10760
-      - dn_target_config_node_list=iotdb-service:10710
+      - dn_target_config_node=iotdb-service:10710
     volumes:
         - ./data:/iotdb/data
         - ./logs:/iotdb/logs
@@ -177,7 +177,7 @@ services:
     container_name: iotdb-confignode
     environment:
       - cn_internal_address=iotdb-2
-      - cn_target_config_node_list=iotdb-1:10710
+      - cn_target_config_node=iotdb-1:10710
       - cn_internal_port=10710
       - cn_consensus_port=10720
       - schema_replication_factor=3
@@ -197,7 +197,7 @@ services:
     environment:
       - dn_rpc_address=iotdb-2
       - dn_internal_address=iotdb-2
-      - dn_target_config_node_list=iotdb-1:10710
+      - dn_target_config_node=iotdb-1:10710
       - data_replication_factor=3
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
@@ -216,7 +216,7 @@ services:
 
 Notice：
 
-1. The `dn_target_config_node_list` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
+1. The `dn_target_config_node` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
 2. In this docker-compose file，`iotdb-2` should be replace with the real IP or hostname of each node to generate docker compose files in the other nodes.
 3. The services would talk with each other, so they need map the /etc/hosts file or add the `extra_hosts` to the docker compose file.
 4. We must start the IoTDB services of `iotdb-1` first at the first time of starting.

src/UserGuide/Master/stage/WayToGetIoTDB.md

@@ -100,12 +100,12 @@ docker run -d --name iotdb-service \
               --ip 172.18.0.6 \
               -p 6667:6667 \
               -e cn_internal_address=iotdb-service \
-              -e cn_target_config_node_list=iotdb-service:10710 \
+              -e cn_target_config_node=iotdb-service:10710 \
               -e cn_internal_port=10710 \
               -e cn_consensus_port=10720 \
               -e dn_rpc_address=iotdb-service \
               -e dn_internal_address=iotdb-service \
-              -e dn_target_config_node_list=iotdb-service:10710 \
+              -e dn_target_config_node=iotdb-service:10710 \
               -e dn_mpp_data_exchange_port=10740 \
               -e dn_schema_region_consensus_port=10750 \
               -e dn_data_region_consensus_port=10760 \
@@ -134,14 +134,14 @@ services:
       - cn_internal_address=iotdb-service
       - cn_internal_port=10710
       - cn_consensus_port=10720
-      - cn_target_config_node_list=iotdb-service:10710
+      - cn_target_config_node=iotdb-service:10710
       - dn_rpc_address=iotdb-service
       - dn_internal_address=iotdb-service
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
       - dn_schema_region_consensus_port=10750
       - dn_data_region_consensus_port=10760
-      - dn_target_config_node_list=iotdb-service:10710
+      - dn_target_config_node=iotdb-service:10710
     volumes:
         - ./data:/iotdb/data
         - ./logs:/iotdb/logs
@@ -167,7 +167,7 @@ services:
     container_name: iotdb-confignode
     environment:
       - cn_internal_address=iotdb-2
-      - cn_target_config_node_list=iotdb-1:10710
+      - cn_target_config_node=iotdb-1:10710
       - cn_internal_port=10710
       - cn_consensus_port=10720
       - schema_replication_factor=3
@@ -187,7 +187,7 @@ services:
     environment:
       - dn_rpc_address=iotdb-2
       - dn_internal_address=iotdb-2
-      - dn_target_config_node_list=iotdb-1:10710
+      - dn_target_config_node=iotdb-1:10710
       - data_replication_factor=3
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
@@ -204,7 +204,7 @@ services:
     network_mode: "host"
 ```
 Notice：
-1. The `dn_target_config_node_list` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
+1. The `dn_target_config_node` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
 2. In this docker-compose file，`iotdb-2` should be replace with the real IP or hostname of each node to generate docker compose files in the other nodes.
 3. The services would talk with each other, so they need map the /etc/hosts file or add the `extra_hosts` to the docker compose file.
 4. We must start the IoTDB services of `iotdb-1` first at the first time of starting.

src/UserGuide/V1.0.x/QuickStart/ClusterQuickStart.md

@@ -84,7 +84,7 @@ It's recommended that the configurations of iotdb-common.properties and the heap
 Before starting the IoTDB cluster, make sure the configurations are correct and there is no any data in the working directory. 
 
 #### 1.3.1. start the first node
-That is `cn_target_config_node_list` in above configuration table.
+That is `cn_target_config_node` in above configuration table.
 Execute these commands below in node of `192.168.132.10`.
 ```shell
 cd /data/iotdb
@@ -99,7 +99,7 @@ tail -f logs/log_datanode_all.log
 If there is no such logs mentioned abolve or there are some `Exception`s in log files, it's failed. Then please check `log_confignode_all.log` and `log_datanode_all.log` in directory of `/data/iotdb/logs`.
 
 **Notice**：
-- Make sure the first node, especially the first ConfigNode that `cn_target_config_node_list` specified, starting successfully, and then start the other services.
+- Make sure the first node, especially the first ConfigNode that `cn_target_config_node` specified, starting successfully, and then start the other services.
 - If starting failed，it's necessary to do [cleanup](#【reference】cleanup) before starting again.
 - How to start service ConfigNode or DataNode alone: 
 ```shell
@@ -173,7 +173,7 @@ It's the same as starting the other nodes mentioned above. That is downloading I
 **Notice**
 - It's must be cleaned up, in other words doing [cleanup](#cleanup) in it.
 - `cluster_name` of `iotdb-common.properties` must be the same to the cluster.
-- `cn_target_config_node_list` and `dn_target_config_node_list` must be the same to the cluster.
+- `cn_target_config_node` and `dn_target_config_node` must be the same to the cluster.
 - The old data wouldn't be moved to the new node but the new data would be.
 
 ### 2.1. configuration

src/UserGuide/V1.0.x/QuickStart/WayToGetIoTDB.md

@@ -100,12 +100,12 @@ docker run -d --name iotdb-service \
               --ip 172.18.0.6 \
               -p 6667:6667 \
               -e cn_internal_address=iotdb-service \
-              -e cn_target_config_node_list=iotdb-service:10710 \
+              -e cn_target_config_node=iotdb-service:10710 \
               -e cn_internal_port=10710 \
               -e cn_consensus_port=10720 \
               -e dn_rpc_address=iotdb-service \
               -e dn_internal_address=iotdb-service \
-              -e dn_target_config_node_list=iotdb-service:10710 \
+              -e dn_target_config_node=iotdb-service:10710 \
               -e dn_mpp_data_exchange_port=10740 \
               -e dn_schema_region_consensus_port=10750 \
               -e dn_data_region_consensus_port=10760 \
@@ -134,13 +134,13 @@ services:
       - cn_internal_address=iotdb-service
       - cn_internal_port=10710
       - cn_consensus_port=10720
-      - cn_target_config_node_list=iotdb-service:10710
+      - cn_target_config_node=iotdb-service:10710
       - dn_rpc_address=iotdb-service
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
       - dn_schema_region_consensus_port=10750
       - dn_data_region_consensus_port=10760
-      - dn_target_config_node_list=iotdb-service:10710
+      - dn_target_config_node=iotdb-service:10710
     volumes:
         - ./data:/iotdb/data
         - ./logs:/iotdb/logs
@@ -166,7 +166,7 @@ services:
     container_name: iotdb-confignode1.0.1-
     environment:
       - cn_internal_address=iotdb-2
-      - cn_target_config_node_list=iotdb-1:10710
+      - cn_target_config_node=iotdb-1:10710
       - cn_internal_port=10710
       - cn_consensus_port=10720
       - schema_replication_factor=3
@@ -186,7 +186,7 @@ services:
     environment:
       - dn_rpc_address=iotdb-2
       - dn_internal_address=iotdb-2
-      - dn_target_config_node_list=iotdb-1:10710
+      - dn_target_config_node=iotdb-1:10710
       - data_replication_factor=3
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
@@ -203,7 +203,7 @@ services:
     network_mode: "host"
 ```
 Notice：
-1. The `dn_target_config_node_list` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
+1. The `dn_target_config_node` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
 2. In this docker-compose file，`iotdb-2` should be replace with the real IP or hostname of each node to generate docker compose files in the other nodes.
 3. The services would talk with each other, so they need map the /etc/hosts file or add the `extra_hosts` to the docker compose file.
 4. We must start the IoTDB services of `iotdb-1` first at the first time of starting.

src/UserGuide/V1.1.x/QuickStart/ClusterQuickStart.md

@@ -84,7 +84,7 @@ It's recommended that the configurations of iotdb-common.properties and the heap
 Before starting the IoTDB cluster, make sure the configurations are correct and there is no any data in the working directory. 
 
 #### 1.3.1. start the first node
-That is `cn_target_config_node_list` in above configuration table.
+That is `cn_target_config_node` in above configuration table.
 Execute these commands below in node of `192.168.132.10`.
 ```shell
 cd /data/iotdb
@@ -99,7 +99,7 @@ tail -f logs/log_datanode_all.log
 If there is no such logs mentioned abolve or there are some `Exception`s in log files, it's failed. Then please check `log_confignode_all.log` and `log_datanode_all.log` in directory of `/data/iotdb/logs`.
 
 **Notice**：
-- Make sure the first node, especially the first ConfigNode that `cn_target_config_node_list` specified, starting successfully, and then start the other services.
+- Make sure the first node, especially the first ConfigNode that `cn_target_config_node` specified, starting successfully, and then start the other services.
 - If starting failed，it's necessary to do [cleanup](#【reference】cleanup) before starting again.
 - How to start service ConfigNode or DataNode alone: 
 ```shell
@@ -173,7 +173,7 @@ It's the same as starting the other nodes mentioned above. That is downloading I
 **Notice**
 - It's must be cleaned up, in other words doing [cleanup](#cleanup) in it.
 - `cluster_name` of `iotdb-common.properties` must be the same to the cluster.
-- `cn_target_config_node_list` and `dn_target_config_node_list` must be the same to the cluster.
+- `cn_target_config_node` and `dn_target_config_node` must be the same to the cluster.
 - The old data wouldn't be moved to the new node but the new data would be.
 
 ### 2.1. configuration

src/UserGuide/V1.1.x/QuickStart/WayToGetIoTDB.md

@@ -100,12 +100,12 @@ docker run -d --name iotdb-service \
               --ip 172.18.0.6 \
               -p 6667:6667 \
               -e cn_internal_address=iotdb-service \
-              -e cn_target_config_node_list=iotdb-service:10710 \
+              -e cn_target_config_node=iotdb-service:10710 \
               -e cn_internal_port=10710 \
               -e cn_consensus_port=10720 \
               -e dn_rpc_address=iotdb-service \
               -e dn_internal_address=iotdb-service \
-              -e dn_target_config_node_list=iotdb-service:10710 \
+              -e dn_target_config_node=iotdb-service:10710 \
               -e dn_mpp_data_exchange_port=10740 \
               -e dn_schema_region_consensus_port=10750 \
               -e dn_data_region_consensus_port=10760 \
@@ -134,14 +134,14 @@ services:
       - cn_internal_address=iotdb-service
       - cn_internal_port=10710
       - cn_consensus_port=10720
-      - cn_target_config_node_list=iotdb-service:10710
+      - cn_target_config_node=iotdb-service:10710
       - dn_rpc_address=iotdb-service
       - dn_internal_address=iotdb-service
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
       - dn_schema_region_consensus_port=10750
       - dn_data_region_consensus_port=10760
-      - dn_target_config_node_list=iotdb-service:10710
+      - dn_target_config_node=iotdb-service:10710
     volumes:
         - ./data:/iotdb/data
         - ./logs:/iotdb/logs
@@ -167,7 +167,7 @@ services:
     container_name: iotdb-confignode
     environment:
       - cn_internal_address=iotdb-2
-      - cn_target_config_node_list=iotdb-1:10710
+      - cn_target_config_node=iotdb-1:10710
       - cn_internal_port=10710
       - cn_consensus_port=10720
       - schema_replication_factor=3
@@ -187,7 +187,7 @@ services:
     environment:
       - dn_rpc_address=iotdb-2
       - dn_internal_address=iotdb-2
-      - dn_target_config_node_list=iotdb-1:10710
+      - dn_target_config_node=iotdb-1:10710
       - data_replication_factor=3
       - dn_rpc_port=6667
       - dn_mpp_data_exchange_port=10740
@@ -204,7 +204,7 @@ services:
     network_mode: "host"
 ```
 Notice：
-1. The `dn_target_config_node_list` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
+1. The `dn_target_config_node` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
 2. In this docker-compose file，`iotdb-2` should be replace with the real IP or hostname of each node to generate docker compose files in the other nodes.
 3. The services would talk with each other, so they need map the /etc/hosts file or add the `extra_hosts` to the docker compose file.
 4. We must start the IoTDB services of `iotdb-1` first at the first time of starting.