From e64f9757d97419568704ce511e2971ee2cd9e004 Mon Sep 17 00:00:00 2001 From: Leto_b Date: Wed, 12 Mar 2025 14:26:27 +0800 Subject: [PATCH] add one clike cluster start and stop in cluster deployment --- .../Cluster-Deployment_apache.md | 71 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 71 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 71 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 72 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 71 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 75 +++++++++++++++++++ .../Cluster-Deployment_apache.md | 71 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 71 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 71 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 71 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 71 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 71 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 73 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 73 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 73 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 72 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 73 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 73 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 73 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 73 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 72 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 73 ++++++++++++++++++ .../Cluster-Deployment_apache.md | 72 ++++++++++++++++++ .../Cluster-Deployment_timecho.md | 71 ++++++++++++++++++ 24 files changed, 1728 insertions(+) diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 29e8e8dae..a097f1414 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -169,6 +169,77 @@ On each server, navigate to the `sbin` directory and start the DataNode: ./start-cli.bat -sql_dialect table ``` +### 3.7 One-click Cluster Start and Stop + +#### 3.7.1 Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### 3.7.2 Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## 4. Maintenance ### 4.1 ConfigNode Maintenance diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index f039b0fca..33311caf1 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -217,6 +217,77 @@ Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database ![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) +### 3.8 One-click Cluster Start and Stop + +#### 3.8.1 Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### 3.8.2 Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## 4. Maintenance ### 4.1 ConfigNode Maintenance diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 568aff270..2ae7d89f2 100644 --- a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -172,6 +172,77 @@ You can use the `show cluster` command to view cluster information: > The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +### 3.6 One-click Cluster Start and Stop + +#### 3.6.1 Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### 3.6.2 Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## 4. Node Maintenance Steps ### 4.1 ConfigNode Node Maintenance diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index 99996d8b7..b373cae89 100644 --- a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -223,6 +223,78 @@ Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database ![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) +### 3.8 One-click Cluster Start and Stop + +#### 3.8.1 Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### 3.8.2 Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + + ## 4. Maintenance ### 4.1 ConfigNode Maintenance diff --git a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md index b11e592fe..0fe7b45c7 100644 --- a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -172,6 +172,77 @@ You can use the `show cluster` command to view cluster information: > The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +### One-click Cluster Start and Stop + +#### Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## Node Maintenance Steps ### ConfigNode Node Maintenance diff --git a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index c3e4362f3..a39498250 100644 --- a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -209,6 +209,81 @@ When you see the display of `Activated` on the far right, it indicates successfu > The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. + +### One-click Cluster Start and Stop + +#### Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + + + + ## Node Maintenance Steps ### ConfigNode Node Maintenance diff --git a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md index cc3be90c6..5935bc99f 100644 --- a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -172,6 +172,77 @@ You can use the `show cluster` command to view cluster information: > The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +### One-click Cluster Start and Stop + +#### Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## Node Maintenance Steps ### ConfigNode Node Maintenance diff --git a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index 6cd68bd26..fdb8284c3 100644 --- a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -209,6 +209,77 @@ When you see the display of `Activated` on the far right, it indicates successfu > The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +### One-click Cluster Start and Stop + +#### Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## Node Maintenance Steps ### ConfigNode Node Maintenance diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 29e8e8dae..a097f1414 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -169,6 +169,77 @@ On each server, navigate to the `sbin` directory and start the DataNode: ./start-cli.bat -sql_dialect table ``` +### 3.7 One-click Cluster Start and Stop + +#### 3.7.1 Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### 3.7.2 Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## 4. Maintenance ### 4.1 ConfigNode Maintenance diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index f039b0fca..33311caf1 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -217,6 +217,77 @@ Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database ![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) +### 3.8 One-click Cluster Start and Stop + +#### 3.8.1 Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### 3.8.2 Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## 4. Maintenance ### 4.1 ConfigNode Maintenance diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 568aff270..2ae7d89f2 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -172,6 +172,77 @@ You can use the `show cluster` command to view cluster information: > The appearance of `ACTIVATED (W)` indicates passive activation, which means that this Configurable Node does not have a license file (or has not issued the latest license file with a timestamp), and its activation depends on other Activated Configurable Nodes in the cluster. At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply. +### 3.6 One-click Cluster Start and Stop + +#### 3.6.1 Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### 3.6.2 Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## 4. Node Maintenance Steps ### 4.1 ConfigNode Node Maintenance diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index 99996d8b7..5ef577588 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -223,6 +223,77 @@ Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database ![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) +### 3.8 One-click Cluster Start and Stop + +#### 3.8.1 Overview + +Within the root directory of IoTDB, the `sbin `subdirectory houses the `start-all.sh` and `stop-all.sh` scripts, which work in concert with the `iotdb-cluster.properties` configuration file located in the `conf` subdirectory. This synergy enables the one-click initiation or termination of all nodes within the cluster from a single node. This approach facilitates efficient management of the IoTDB cluster's lifecycle, streamlining the deployment and operational maintenance processes. + +This following section will introduce the specific configuration items in the `iotdb-cluster.properties` file. + +#### 3.8.2 Configuration Items + +> Note: +> +> * When the cluster changes, this configuration file needs to be manually updated. +> * If the `iotdb-cluster.properties` configuration file is not set up and the `start-all.sh` or `stop-all.sh` scripts are executed, the scripts will, by default, start or stop the ConfigNode and DataNode nodes located in the IOTDB\_HOME directory where the scripts reside. +> * It is recommended to configure SSH passwordless login: If not configured, the script will prompt for the server password after execution to facilitate subsequent start, stop, or destroy operations. If already configured, there is no need to enter the server password during script execution. + +* confignode\_address\_list + +| **Name** | **confignode\_address\_list** | +| :----------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the ConfigNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_address\_list + +| **Name** | **datanode\_address\_list** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | A list of IP addresses of the hosts where the DataNodes to be started/stopped are located. If there are multiple, they should be separated by commas. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* ssh\_account + +| **Name** | **ssh\_account** | +| :----------------: | :------------------------------------------------------------------------------------------------- | +| Description | The username used to log in to the target hosts via SSH. All hosts must have the same username. | +| Type | String | +| Default | root | +| Effective | After restarting the system | + +* ssh\_port + +| **Name** | **ssh\_port** | +| :----------------: | :---------------------------------------------------------------------------------- | +| Description | The SSH port exposed by the target hosts. All hosts must have the same SSH port. | +| Type | int | +| Default | 22 | +| Effective | After restarting the system | + +* confignode\_deploy\_path + +| **Name** | **confignode\_deploy\_path** | +| :----------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Description | The path on the target hosts where all ConfigNodes to be started/stopped are located. All ConfigNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + +* datanode\_deploy\_path + +| **Name** | **datanode\_deploy\_path** | +| :----------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Description | The path on the target hosts where all DataNodes to be started/stopped are located. All DataNodes must be in the same directory on their respective hosts. | +| Type | String | +| Default | None | +| Effective | After restarting the system | + + ## 4. Maintenance ### 4.1 ConfigNode Maintenance diff --git a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md index b9b82e0e4..c260e69a0 100644 --- a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -166,6 +166,79 @@ cd sbin ./start-cli.bat -sql_dialect table ``` + +### 3.6 一键启停集群 + +#### 3.6.1 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 3.6.2 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 4. 节点维护步骤 ### 4.1 ConfigNode节点维护 diff --git a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index 2768d6dfb..6daedfec6 100644 --- a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -220,6 +220,79 @@ cd sbin ![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) + +### 3.7 一键启停集群 + +#### 3.7.1 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 3.7.2 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 4. 节点维护步骤 ### 4.1 ConfigNode节点维护 diff --git a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 6d26a4e33..b06cef74a 100644 --- a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -170,6 +170,79 @@ cd sbin > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + +### 3.6 一键启停集群 + +#### 3.6.1 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 3.6.2 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 4. 节点维护步骤 ### 4.1 ConfigNode节点维护 diff --git a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index fec4e9967..a6395b0a9 100644 --- a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -208,6 +208,78 @@ cd sbin > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + +### 3.7 一键启停集群 + +#### 3.7.1 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 3.7.2 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + ## 4. 节点维护步骤 ### 4.1 ConfigNode节点维护 diff --git a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 6603bd7c8..7da20c7e1 100644 --- a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -170,6 +170,79 @@ cd sbin > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + +### 一键启停集群 + +#### 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 节点维护步骤 ### ConfigNode节点维护 diff --git a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index 933476514..d0fda022a 100644 --- a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -208,6 +208,79 @@ cd sbin > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + +### 一键启停集群 + +#### 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 节点维护步骤 ### ConfigNode节点维护 diff --git a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 428a9426a..44961abae 100644 --- a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -170,6 +170,79 @@ cd sbin > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + +### 一键启停集群 + +#### 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 节点维护步骤 ### ConfigNode节点维护 diff --git a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index 8f17ab089..c10d2f635 100644 --- a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -208,6 +208,79 @@ cd sbin > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + +### 一键启停集群 + +#### 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 节点维护步骤 ### ConfigNode节点维护 diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md index b9b82e0e4..ee7bd741f 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -166,6 +166,78 @@ cd sbin ./start-cli.bat -sql_dialect table ``` +### 3.6 一键启停集群 + +#### 3.6.1 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 3.6.2 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 4. 节点维护步骤 ### 4.1 ConfigNode节点维护 diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index 2768d6dfb..6daedfec6 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -220,6 +220,79 @@ cd sbin ![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) + +### 3.7 一键启停集群 + +#### 3.7.1 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 3.7.2 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 4. 节点维护步骤 ### 4.1 ConfigNode节点维护 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md index 6d26a4e33..a5353dfed 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md @@ -170,6 +170,78 @@ cd sbin > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. +### 3.6 一键启停集群 + +#### 3.6.1 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 3.6.2 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + + ## 4. 节点维护步骤 ### 4.1 ConfigNode节点维护 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md index fec4e9967..7af89344f 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -208,6 +208,77 @@ cd sbin > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. +### 3.7 一键启停集群 + +#### 3.7.1 概述 + +在 IoTDB 的根目录中，`sbin` 子目录包含的 `start-all.sh` 和 `stop-all.sh` 脚本，与 `conf` 子目录中的 `iotdb-cluster.properties` 配置文件协同工作，可通过单一节点实现一键启动或停止集群所有节点的功能。通过这种方式，可以高效地管理 IoTDB 集群的生命周期，简化了部署和运维流程。 +下文将介绍`iotdb-cluster.properties` 文件中的具体配置项。 + +#### 3.7.2 配置项 + + +> 注意： +> +> * 当集群变更时，需要手动更新此配置文件。 +> * 如果在未配置 `iotdb-cluster.properties` 配置文件的情况下执行 `start-all.sh` 或者 `stop-all.sh` 脚本，则默认会启停当前脚本所在 IOTDB\_HOME 目录下的 ConfigNode 与 DataNode 节点。 +> * 推荐配置 ssh 免密登录：如果未配置，启动脚本后会提示输入服务器密码以便于后续启动/停止/销毁操作。如果已配置，则无需在执行脚本过程中输入服务器密码。 + +* confignode\_address\_list + +| 名字 | confignode\_address\_list | +| :--------------: | :------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的 ConfigNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_address\_list + +| 名字 | datanode\_address\_list | +| :----------------: | :---------------------------------------------------------------------------- | +| 描述 | 待启动/停止的 DataNode 节点所在主机的 IP 列表，如果有多个需要用“,”分隔。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* ssh\_account + +| 名字 | ssh\_account | +| :----------------: | :------------------------------------------------------------- | +| 描述 | 通过 SSH 登陆目标主机的用户名，需要所有的主机的用户名都相同 | +| 类型 | String | +| 默认值 | root | +| 改后生效方式 | 重启服务生效 | + +* ssh\_port + +| 名字 | ssh\_port | +| :----------------: | :--------------------------------------------------------- | +| 描述 | 目标主机对外暴露的 SSH 端口，需要所有的主机的端口都相同 | +| 类型 | int | +| 默认值 | 22 | +| 改后生效方式 | 重启服务生效 | + +* confignode\_deploy\_path + +| 名字 | confignode\_deploy\_path | +| :----------------: | :---------------------------------------------------------------------------------------------------------------- | +| 描述 | 待启动/停止的所有 ConfigNode 所在目标主机的路径，需要所有待启动/停止的 ConfigNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + +* datanode\_deploy\_path + +| 名字 | datanode\_deploy\_path | +| :----------------: | :------------------------------------------------------------------------------------------------------------ | +| 描述 | 待启动/停止的所有 DataNode 所在目标主机的路径，需要所有待启动/停止的 DataNode 节点在目标主机的相同目录下。 | +| 类型 | String | +| 默认值 | 无 | +| 改后生效方式 | 重启服务生效 | + + ## 4. 节点维护步骤 ### 4.1 ConfigNode节点维护