cluster deployment document optimization

src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -142,6 +142,9 @@ cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
 
+If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+
+
 ### Start DataNode
 
  Enter the `sbin` directory of iotdb and start three datanode nodes in sequence:
@@ -306,3 +309,39 @@ sbin/remove-datanode.sh [datanode_id]
 #Windows
 sbin/remove-datanode.bat [datanode_id]
 ```
+## Common Questions
+
+1. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```

src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -142,6 +142,9 @@ cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
 
+If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+
+
 ### Activate Database
 
 #### Method 1: Activate file copy activation
@@ -344,7 +347,42 @@ sbin/remove-datanode.sh [datanode_id]
 sbin/remove-datanode.bat [datanode_id]
 ```
 
-## Common Problem
+## Common Questions
 1. Multiple prompts indicating activation failure during deployment process
     - Use the `ls -al` command: Use the `ls -al` command to check if the owner information of the installation package root directory is the current user.
-    - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+    - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+
+2. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```

src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -142,6 +142,8 @@ cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
 
+If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+
 ### Start DataNode
 
  Enter the `sbin` directory of iotdb and start three datanode nodes in sequence:
@@ -306,4 +308,41 @@ sbin/remove-datanode.sh [dn_rpc_address:dn_rpc_port]
 
 #Windows
 sbin/remove-datanode.bat [dn_rpc_address:dn_rpc_port]
-```
+```
+
+## Common Questions
+
+1. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```

src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -142,6 +142,7 @@ Start the first confignode of IoTDB-1 first, ensuring that the seed confignode n
 cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
+If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
 
 ### Activate Database
 
@@ -347,7 +348,42 @@ sbin/remove-datanode.sh [dn_rpc_address:dn_rpc_port]
 sbin/remove-datanode.bat [dn_rpc_address:dn_rpc_port]
 ```
 
-## Common Problem
+## Common Questions
 1. Multiple prompts indicating activation failure during deployment process
     - Use the `ls -al` command: Use the `ls -al` command to check if the owner information of the installation package root directory is the current user.
-    - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+    - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+
+2. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```

src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -141,6 +141,7 @@ cd  apache-iotdb-{version}-all-bin
 cd sbin
 ./start-confignode.sh    -d      #“-d”参数将在后台进行启动 
 ```
+如果启动失败，请到[常见问题](#常见问题)查看解决方案。
 
 ### 启动DataNode 节点
 
@@ -305,4 +306,38 @@ sbin/remove-datanode.sh [datanode_id]
 
 #Windows
 sbin/remove-datanode.bat [datanode_id]
-```
+```
+
+## 常见问题
+
+1.  启动confignode的命令后，节点多次启动失败或出现运行错误的提示？
+
+    步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
+
+    步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。
+
+    步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
+
+    清理环境：
+   1. 结束所有 ConfigNode 和 DataNode 进程。
+   ```Bash
+    # 1. 停止 ConfigNode 和 DataNode 服务
+    sbin/stop-standalone.sh
+
+    # 2. 检查是否还有进程残留
+    jps
+    # 或者
+    ps -ef|gerp iotdb
+
+    # 3. 如果有进程残留，则手动kill
+    kill -9 <pid>
+    # 如果确定机器上仅有1个iotdb，可以使用下面命令清理残留进程
+    ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  删除 data 和 logs 目录。 
+
+   说明：删除 data 目录是必要的，删除 logs 目录是为了纯净日志，非必需。
+   ```Bash
+    cd /data/iotdb
+    rm -rf data logs
+   ```

src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -142,6 +142,7 @@ cd  iotdb-enterprise-{version}-bin
 cd sbin
 ./start-confignode.sh    -d      #“-d”参数将在后台进行启动 
 ```
+如果启动失败，请到[常见问题](#常见问题)查看解决方案。
 
 ### 激活数据库
 
@@ -349,4 +350,36 @@ sbin/remove-datanode.bat [datanode_id]
 
 1. 部署过程中多次提示激活失败
     - 使用 `ls -al` 命令：使用 `ls -al` 命令检查安装包根目录的所有者信息是否为当前用户。
-    - 检查激活目录：检查 `./activation` 目录下的所有文件，所有者信息是否为当前用户。  
+    - 检查激活目录：检查 `./activation` 目录下的所有文件，所有者信息是否为当前用户。  
+
+2. 启动confignode的命令后，节点多次启动失败或出现运行错误的提示？
+
+    步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
+
+    步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。
+
+    步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
+
+    清理环境：
+   1. 结束所有 ConfigNode 和 DataNode 进程。
+   ```Bash
+    # 1. 停止 ConfigNode 和 DataNode 服务
+    sbin/stop-standalone.sh
+
+    # 2. 检查是否还有进程残留
+    jps
+    # 或者
+    ps -ef|gerp iotdb
+
+    # 3. 如果有进程残留，则手动kill
+    kill -9 <pid>
+    # 如果确定机器上仅有1个iotdb，可以使用下面命令清理残留进程
+    ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  删除 data 和 logs 目录。 
+
+   说明：删除 data 目录是必要的，删除 logs 目录是为了纯净日志，非必需。
+   ```Bash
+    cd /data/iotdb
+    rm -rf data logs
+   ```

src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -141,6 +141,7 @@ cd  apache-iotdb-{version}-all-bin
 cd sbin
 ./start-confignode.sh    -d      #“-d”参数将在后台进行启动 
 ```
+如果启动失败，请参考[常见问题](#常见问题)。
 
 ### 启动DataNode 节点
 
@@ -305,4 +306,38 @@ sbin/remove-datanode.sh [dn_rpc_address:dn_rpc_port]
 
 #Windows
 sbin/remove-datanode.bat [dn_rpc_address:dn_rpc_port]
-```
+```
+
+## 常见问题
+
+1. Confignode节点启动失败
+
+    步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
+
+    步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系天谋技术支持人员咨询解决方案。
+
+    步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
+
+    清理环境：
+   1. 结束所有 ConfigNode 和 DataNode 进程。
+   ```Bash
+    # 1. 停止 ConfigNode 和 DataNode 服务
+    sbin/stop-standalone.sh
+
+    # 2. 检查是否还有进程残留
+    jps
+    # 或者
+    ps -ef|gerp iotdb
+
+    # 3. 如果有进程残留，则手动kill
+    kill -9 <pid>
+    # 如果确定机器上仅有1个iotdb，可以使用下面命令清理残留进程
+    ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  删除 data 和 logs 目录。 
+
+   说明：删除 data 目录是必要的，删除 logs 目录是为了纯净日志，非必需。
+   ```Bash
+    cd /data/iotdb
+    rm -rf data logs
+   ```