This is an automated email from the ASF dual-hosted git repository.
zhaoxinyi pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iotdb-docs.git
The following commit(s) were added to refs/heads/main by this push:
new b824a135 update cluster activation via cli (#796)
b824a135 is described below
commit b824a13547c705ac534c435f76d1f5afaf9a7190
Author: leto-b <[email protected]>
AuthorDate: Wed Jul 23 14:10:09 2025 +0800
update cluster activation via cli (#796)
* update cluster activation via cli
* Adjust the order of activation methods
* adjust activate database of 1.3.x
---
.../Cluster-Deployment_timecho.md | 28 +++----
.../Stand-Alone-Deployment_timecho.md | 26 +++---
.../Cluster-Deployment_timecho.md | 30 +++----
.../Stand-Alone-Deployment_timecho.md | 28 +++----
.../Cluster-Deployment_timecho.md | 73 ++++++++++++++--
.../Stand-Alone-Deployment_timecho.md | 69 +++++++++++++--
.../Cluster-Deployment_timecho.md | 98 +++++++++++++++++++---
.../Stand-Alone-Deployment_timecho.md | 69 +++++++++++++--
.../Cluster-Deployment_timecho.md | 28 +++----
.../Stand-Alone-Deployment_timecho.md | 25 ++----
.../Cluster-Deployment_timecho.md | 30 +++----
.../Stand-Alone-Deployment_timecho.md | 28 +++----
.../Cluster-Deployment_timecho.md | 35 ++++----
.../Stand-Alone-Deployment_timecho.md | 24 +++---
.../Cluster-Deployment_timecho.md | 35 ++++----
.../Stand-Alone-Deployment_timecho.md | 26 +++---
.../Cluster-Deployment_timecho.md | 71 ++++++++++++++--
.../Stand-Alone-Deployment_timecho.md | 67 +++++++++++++--
.../Cluster-Deployment_timecho.md | 94 +++++++++++++++++----
.../Stand-Alone-Deployment_timecho.md | 67 +++++++++++++--
.../Cluster-Deployment_timecho.md | 35 ++++----
.../Stand-Alone-Deployment_timecho.md | 24 +++---
.../Cluster-Deployment_timecho.md | 35 ++++----
.../Stand-Alone-Deployment_timecho.md | 24 ++----
24 files changed, 716 insertions(+), 353 deletions(-)
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 1d49f04a..0a7f3d3d 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
@@ -159,15 +159,9 @@ On each server, navigate to the `sbin` directory and start
the DataNode:
### 3.6 Activate the Database
-#### Option 1: File-Based Activation
+#### Option 1: Command-Based Activation
-1. Start all ConfigNodes and DataNodes.
-2. Copy the `system_info` file from the `activation` directory on each server
and send them to the Timecho team.
-3. Place the license files provided by the Timecho team into the corresponding
`activation` folder for each node.
-
-#### Option 2: Command-Based Activation
-
-1. Enter the IoTDB CLI for each node:
+1. Enter the IoTDB CLI on any node of the cluster:
- **For Table Model**:
```SQL
# For Linux or macOS
@@ -177,14 +171,6 @@ On each server, navigate to the `sbin` directory and start
the DataNode:
./start-cli.bat -sql_dialect table
```
- - **For Tree Model**:
- ```SQL
- # For Linux or macOS
- ./start-cli.sh
-
- # For Windows
- ./start-cli.bat
- ```
2. Run the following command to retrieve the machine code required for
activation:
```Bash
@@ -192,7 +178,7 @@ On each server, navigate to the `sbin` directory and start
the DataNode:
```
-3. Copy the returned machine code of each server (displayed as a green string)
and send it to the Timecho team:
+3. Copy the returned machine codes of all nodes in the cluster (displayed as a
green string) and send it to the Timecho team:
```Bash
+--------------------------------------------------------------+
@@ -210,6 +196,14 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,0
[...]
```
+
+#### Option 2: File-Based Activation
+
+1. Start all ConfigNodes and DataNodes.
+2. Copy the `system_info` file from the `activation` directory on each server
and send them to the Timecho team.
+3. Place the license files provided by the Timecho team into the corresponding
`activation` folder for each node.
+
+
### 3.7 Verify Activation
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the
database has been successfully activated.
diff --git
a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 79c1d802..8ff01913 100644
---
a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -126,14 +126,7 @@ Navigate to the `sbin` directory of IoTDB and start the
DataNode:
### 2.5 Activate the Database
-#### Option 1: File-Based Activation
-
-- Start both the ConfigNode and DataNode.
-- Navigate to the `activation` folder and copy the `system_info` file.
-- Send the `system_info` file to the Timecho team.
-- Place the license file provided by the Timecho team into the corresponding
`activation` folder for each node.
-
-#### Option 2: Command-Based Activation
+#### Option 1: Command-Based Activation
1. Enter the IoTDB CLI.
- **For Table Model**:
@@ -145,14 +138,6 @@ Navigate to the `sbin` directory of IoTDB and start the
DataNode:
./start-cli.bat -sql_dialect table
```
- - **For Tree Model**:
- - ```SQL
- # For Linux or macOS
- ./start-cli.sh
-
- # For Windows
- ./start-cli.bat
- ```
2. Run the following command to retrieve the machine code required for
activation:
```Bash
@@ -177,6 +162,15 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
```
+
+#### Option 2: File-Based Activation
+
+- Start both the ConfigNode and DataNode.
+- Navigate to the `activation` folder and copy the `system_info` file.
+- Send the `system_info` file to the Timecho team.
+- Place the license file provided by the Timecho team into the corresponding
`activation` folder for each node.
+
+
### 2.6 Verify Activation
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the
database has been successfully activated.
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 29415899..22d8da6a 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
@@ -161,25 +161,9 @@ cd sbin
### 3.6 Activate Database
-#### Option 1: File-Based Activation
+#### Option 1: Command-Based Activation
-1. Start all ConfigNodes and DataNodes.
-2. Copy the `system_info` file from the `activation` directory on each server
and send them to the Timecho team.
-3. Place the license files provided by the Timecho team into the corresponding
`activation` folder for each node.
-
-#### Option 2: Command-Based Activation
-
-1. Enter the IoTDB CLI for each node:
-
-- **For Table Model**:
-
- ```SQL
- # For Linux or macOS
- ./start-cli.sh -sql_dialect table
-
- # For Windows
- ./start-cli.bat -sql_dialect table
- ```
+1. Enter the IoTDB CLI on any node of the cluster:
- **For Tree Model**:
@@ -197,7 +181,7 @@ cd sbin
show system info
```
-3. Copy the returned machine code of each server (displayed as a green string)
and send it to the Timecho team:
+3. Copy the returned machine codes of all nodes in the cluster (displayed as a
green string) and send it to the Timecho team:
```Bash
+--------------------------------------------------------------+
@@ -215,6 +199,14 @@ cd sbin
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
```
+
+#### Option 2: File-Based Activation
+
+1. Start all ConfigNodes and DataNodes.
+2. Copy the `system_info` file from the `activation` directory on each server
and send them to the Timecho team.
+3. Place the license files provided by the Timecho team into the corresponding
`activation` folder for each node.
+
+
### 3.7 Verify Activation
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the
database has been successfully activated.
diff --git
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 6c454ce5..a6f8e683 100644
---
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -124,27 +124,10 @@ Navigate to the `sbin` directory of IoTDB and start the
DataNode:
### 2.5 Activate Database
-#### Option 1: File-Based Activation
-
-1. Start both the ConfigNode and DataNode.
-2. Navigate to the `activation` folder and copy the `system_info` file.
-3. Send the `system_info` file to the Timecho team.
-4. Place the license file provided by the Timecho team into the corresponding
`activation` folder for each node.
-
-#### Option 2: Command-Based Activation
+#### Option 1: Command-Based Activation
1. Enter the IoTDB CLI.
-- **For Table Model**:
-
-```SQL
-# For Linux or macOS
-./start-cli.sh -sql_dialect table
-
-# For Windows
-./start-cli.bat -sql_dialect table
-```
-
- **For Tree Model**:
```SQL
@@ -179,6 +162,15 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
```
+
+#### Option 2: File-Based Activation
+
+1. Start both the ConfigNode and DataNode.
+2. Navigate to the `activation` folder and copy the `system_info` file.
+3. Send the `system_info` file to the Timecho team.
+4. Place the license file provided by the Timecho team into the corresponding
`activation` folder for each node.
+
+
### 2.6 Verify Activation
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the
database has been successfully activated.
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 0c3db00c..f4bb4de0 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
@@ -133,27 +133,87 @@ Open DataNode Configuration File
`./conf/iotdb-system.properties`,Set the follow
> ❗️Attention: Editors such as VSCode Remote do not have automatic
> configuration saving function. Please ensure that the modified files are
> saved persistently, otherwise the configuration items will not take effect
-### Start ConfigNode
+### Start and Activate Database (Available since V1.3.4)
+
+#### Start ConfigNode
Start the first confignode of IoTDB-1 first, ensuring that the seed confignode
node starts first, and then start the second and third confignode nodes in
sequence
```Bash
-cd sbin
./start-confignode.sh -d #"- d" parameter will start in the background
```
If the startup fails, please refer to [Common Questions](#common-questions).
+#### Start DataNode
+
+Enter the `sbin` directory of iotdb and start three datanode nodes in sequence:
+
+```Bash
+./start-datanode.sh -d #"- d" parameter will start in the background
+```
+
+#### Activate Database
+
+##### Activation via CLI
+
+- Enter the CLI of any node in the cluster
+
+ ```SQL
+ ./sbin/start-cli.sh
+```
+
+- Obtain the machine codes of all nodes:
+
+ - Execute the following command to get the machine codes required for
activation:
+
+ ```Bash
+ show system info
+ ```
+
+ - The machine codes of all nodes in the cluster will be displayed:
+
+ ```Bash
+ +--------------------------------------------------------------+
+ | SystemInfo|
+ +--------------------------------------------------------------+
+ |01-TE5NLES4-UDDWCMYE,01-GG5NLES4-XXDWCMYE,01-FF5NLES4-WWWWCMYE|
+ +--------------------------------------------------------------+
+ Total line number = 1
+ It costs 0.030s
+ ```
+
+- Copy the obtained machine codes and provide them to the Timecho team
+
+- The Timecho team will return an activation code, which normally corresponds
to the order of the provided machine codes. Paste the complete activation code
into the CLI for activation
+
+ - Note: The activation code must be enclosed in ' symbols, as shown below:
+
+ ```Bash
+ IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
+ ```
+
+### Start and Activate Database (Available before V1.3.4)
+
+#### Start ConfigNode
+
+Start the first confignode of IoTDB-1 first, ensuring that the seed confignode
node starts first, and then start the second and third confignode nodes in
sequence
+
+```Bash
+./start-confignode.sh -d #"- d" parameter will start in the background
+```
+
+If the startup fails, please refer to [Common Questions](#common-questions).
-### Activate Database
+#### Activate Database
-#### Method 1: Activate file copy activation
+##### Method 1: Activate file copy activation
- After starting three confignode nodes in sequence, copy the `activation`
folder of each machine and the `system_info` file of each machine to the
Timecho staff;
- The staff will return the license files for each ConfigNode node, where 3
license files will be returned;
- Put the three license files into the `activation` folder of the
corresponding ConfigNode node;
-#### Method 2: Activate Script Activation
+##### Method 2: Activate Script Activation
- Obtain the machine codes of three machines in sequence, enter the `sbin`
directory of the installation directory, and execute the activation script
`start activate.sh`:
@@ -180,12 +240,11 @@ If the startup fails, please refer to [Common
Questions](#common-questions).
Import completed. Please start cluster and excute 'show cluster' to verify
activation status
```
-### Start DataNode
+#### Start DataNode
Enter the `sbin` directory of iotdb and start three datanode nodes in
sequence:
```Bash
-cd sbin
./start-datanode.sh -d #"- d" parameter will start in the background
```
diff --git
a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 19681a33..68fd26ec 100644
---
a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -107,7 +107,63 @@ Open the DataNode configuration file (./conf/iotdb-system.
properties file) and
> ❗️Attention: Editors such as VSCode Remote do not have automatic
> configuration saving function. Please ensure that the modified files are
> saved persistently, otherwise the configuration items will not take effect
-### 3、Start ConfigNode
+### 3. Start and Activate Database (Available since V1.3.4)
+
+#### 3.1 Start ConfigNode
+
+Enter the sbin directory of iotdb and start confignode
+
+```shell
+./start-confignode.sh -d #The "- d" parameter will start in the
background
+```
+If the startup fails, please refer to [Common Questions](#common-questions).
+
+#### 3.2 Start DataNode
+
+Enter the sbin directory of iotdb and start datanode:
+
+```shell
+./start-datanode.sh -d # The "- d" parameter will start in the background
+```
+
+#### 3.3 Activate Database
+
+##### Activation via CLI
+
+- Enter the CLI
+
+ ```SQL
+ ./sbin/start-cli.sh
+```
+
+- Execute the following command to obtain the machine code required for
activation:
+
+ ```Bash
+ show system info
+ ```
+
+- Copy the returned machine code (the green string) and provide it to the
Timecho team:
+
+```Bash
++--------------------------------------------------------------+
+| SystemInfo|
++--------------------------------------------------------------+
+| 01-TE5NLES4-UDDWCMYE|
++--------------------------------------------------------------+
+Total line number = 1
+It costs 0.030s
+```
+
+- Input the activation code returned by the Timecho team into the CLI using
the following command:
+ - Note: The activation code must be enclosed in ' symbols, as shown:
+
+```Bash
+IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
+```
+
+### 4. Start and Activate Database (Available before V1.3.4)
+
+#### 4.1 Start ConfigNode
Enter the sbin directory of iotdb and start confignode
@@ -116,15 +172,15 @@ Enter the sbin directory of iotdb and start confignode
```
If the startup fails, please refer to [Common Questions](#common-questions).
-### 4、Activate Database
+#### 4.2 Activate Database
-#### Method 1: Activate file copy activation
+##### Method 1: Activate file copy activation
- After starting the confignode node, enter the activation folder and copy the
systeminfo file to the Timecho staff
- Received the license file returned by the staff
- Place the license file in the activation folder of the corresponding node;
-#### Method 2: Activate Script Activation
+##### Method 2: Activate Script Activation
- Obtain the required machine code for activation, enter the sbin directory of
the installation directory, and execute the activation script:
@@ -150,16 +206,15 @@ License has been stored to sbin/../activation/license
Import completed. Please start cluster and excute 'show cluster' to verify
activation status
```
-### 5、Start DataNode
+#### 4.3 Start DataNode
Enter the sbin directory of iotdb and start datanode:
```shell
-cd sbin
./start-datanode.sh -d # The "- d" parameter will start in the background
```
-### 6、Verify Deployment
+### 5、Verify Deployment
Can be executed directly/ Cli startup script in sbin directory:
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 54b88519..f4bb4de0 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
@@ -133,27 +133,87 @@ Open DataNode Configuration File
`./conf/iotdb-system.properties`,Set the follow
> ❗️Attention: Editors such as VSCode Remote do not have automatic
> configuration saving function. Please ensure that the modified files are
> saved persistently, otherwise the configuration items will not take effect
-### Start ConfigNode
+### Start and Activate Database (Available since V1.3.4)
+
+#### Start ConfigNode
Start the first confignode of IoTDB-1 first, ensuring that the seed confignode
node starts first, and then start the second and third confignode nodes in
sequence
```Bash
-cd sbin
./start-confignode.sh -d #"- d" parameter will start in the background
```
If the startup fails, please refer to [Common Questions](#common-questions).
+#### Start DataNode
+
+Enter the `sbin` directory of iotdb and start three datanode nodes in sequence:
+
+```Bash
+./start-datanode.sh -d #"- d" parameter will start in the background
+```
+
+#### Activate Database
+
+##### Activation via CLI
+
+- Enter the CLI of any node in the cluster
+
+ ```SQL
+ ./sbin/start-cli.sh
+```
+
+- Obtain the machine codes of all nodes:
+
+ - Execute the following command to get the machine codes required for
activation:
+
+ ```Bash
+ show system info
+ ```
+
+ - The machine codes of all nodes in the cluster will be displayed:
+
+ ```Bash
+ +--------------------------------------------------------------+
+ | SystemInfo|
+ +--------------------------------------------------------------+
+ |01-TE5NLES4-UDDWCMYE,01-GG5NLES4-XXDWCMYE,01-FF5NLES4-WWWWCMYE|
+ +--------------------------------------------------------------+
+ Total line number = 1
+ It costs 0.030s
+ ```
+
+- Copy the obtained machine codes and provide them to the Timecho team
+
+- The Timecho team will return an activation code, which normally corresponds
to the order of the provided machine codes. Paste the complete activation code
into the CLI for activation
+
+ - Note: The activation code must be enclosed in ' symbols, as shown below:
+
+ ```Bash
+ IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
+ ```
+
+### Start and Activate Database (Available before V1.3.4)
+
+#### Start ConfigNode
+
+Start the first confignode of IoTDB-1 first, ensuring that the seed confignode
node starts first, and then start the second and third confignode nodes in
sequence
+
+```Bash
+./start-confignode.sh -d #"- d" parameter will start in the background
+```
+
+If the startup fails, please refer to [Common Questions](#common-questions).
-### Activate Database
+#### Activate Database
-#### Method 1: Activate file copy activation
+##### Method 1: Activate file copy activation
- After starting three confignode nodes in sequence, copy the `activation`
folder of each machine and the `system_info` file of each machine to the
Timecho staff;
- The staff will return the license files for each ConfigNode node, where 3
license files will be returned;
- Put the three license files into the `activation` folder of the
corresponding ConfigNode node;
-#### Method 2: Activate Script Activation
+##### Method 2: Activate Script Activation
- Obtain the machine codes of three machines in sequence, enter the `sbin`
directory of the installation directory, and execute the activation script
`start activate.sh`:
@@ -180,12 +240,11 @@ If the startup fails, please refer to [Common
Questions](#common-questions).
Import completed. Please start cluster and excute 'show cluster' to verify
activation status
```
-### Start DataNode
+#### Start DataNode
Enter the `sbin` directory of iotdb and start three datanode nodes in
sequence:
```Bash
-cd sbin
./start-datanode.sh -d #"- d" parameter will start in the background
```
@@ -209,6 +268,7 @@ 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 t [...]
+
### One-click Cluster Start and Stop
#### Overview
@@ -280,6 +340,9 @@ This following section will introduce the specific
configuration items in the `i
| Effective | After restarting the system
|
+
+
+
## Node Maintenance Steps
### ConfigNode Node Maintenance
@@ -321,7 +384,7 @@ Parameter introduction:
#### Removing ConfigNode Nodes
-First connect to the cluster through the CLI and confirm the NodeID of the
ConfigNode you want to remove by using `show confignodes`:
+First connect to the cluster through the CLI and confirm the internal address
and port number of the ConfigNode you want to remove by using `show
confignodes`:
```Bash
IoTDB> show confignodes
@@ -336,10 +399,15 @@ Total line number = 3
It costs 0.030s
```
-Then use the SQL to remove the ConfigNode. SQL command:
+Then use the script to remove the ConfigNode. Script command:
```Bash
-remove confignode [confignode_id]
+# Linux / MacOS
+sbin/remove-confignode.sh [confignode_id]
+
+#Windows
+sbin/remove-confignode.bat [confignode_id]
+
```
### DataNode Node Maintenance
@@ -385,7 +453,7 @@ Note: After adding a DataNode, as new writes arrive (and
old data expires, if TT
#### Removing DataNode Nodes
-First connect to the cluster through the CLI and confirm the NodeID of the
DataNode you want to remove with `show datanodes`:
+First connect to the cluster through the CLI and confirm the RPC address and
port number of the DataNode you want to remove with `show datanodes`:
```Bash
IoTDB> show datanodes
@@ -400,10 +468,14 @@ Total line number = 3
It costs 0.110s
```
-Then use the SQL to remove the DataNode. SQL command:
+Then use the script to remove the DataNode. Script command:
```Bash
-remove datanode [datanode_id]
+# Linux / MacOS
+sbin/remove-datanode.sh [datanode_id]
+
+#Windows
+sbin/remove-datanode.bat [datanode_id]
```
## Common Questions
diff --git
a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 19681a33..68fd26ec 100644
---
a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -107,7 +107,63 @@ Open the DataNode configuration file (./conf/iotdb-system.
properties file) and
> ❗️Attention: Editors such as VSCode Remote do not have automatic
> configuration saving function. Please ensure that the modified files are
> saved persistently, otherwise the configuration items will not take effect
-### 3、Start ConfigNode
+### 3. Start and Activate Database (Available since V1.3.4)
+
+#### 3.1 Start ConfigNode
+
+Enter the sbin directory of iotdb and start confignode
+
+```shell
+./start-confignode.sh -d #The "- d" parameter will start in the
background
+```
+If the startup fails, please refer to [Common Questions](#common-questions).
+
+#### 3.2 Start DataNode
+
+Enter the sbin directory of iotdb and start datanode:
+
+```shell
+./start-datanode.sh -d # The "- d" parameter will start in the background
+```
+
+#### 3.3 Activate Database
+
+##### Activation via CLI
+
+- Enter the CLI
+
+ ```SQL
+ ./sbin/start-cli.sh
+```
+
+- Execute the following command to obtain the machine code required for
activation:
+
+ ```Bash
+ show system info
+ ```
+
+- Copy the returned machine code (the green string) and provide it to the
Timecho team:
+
+```Bash
++--------------------------------------------------------------+
+| SystemInfo|
++--------------------------------------------------------------+
+| 01-TE5NLES4-UDDWCMYE|
++--------------------------------------------------------------+
+Total line number = 1
+It costs 0.030s
+```
+
+- Input the activation code returned by the Timecho team into the CLI using
the following command:
+ - Note: The activation code must be enclosed in ' symbols, as shown:
+
+```Bash
+IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
+```
+
+### 4. Start and Activate Database (Available before V1.3.4)
+
+#### 4.1 Start ConfigNode
Enter the sbin directory of iotdb and start confignode
@@ -116,15 +172,15 @@ Enter the sbin directory of iotdb and start confignode
```
If the startup fails, please refer to [Common Questions](#common-questions).
-### 4、Activate Database
+#### 4.2 Activate Database
-#### Method 1: Activate file copy activation
+##### Method 1: Activate file copy activation
- After starting the confignode node, enter the activation folder and copy the
systeminfo file to the Timecho staff
- Received the license file returned by the staff
- Place the license file in the activation folder of the corresponding node;
-#### Method 2: Activate Script Activation
+##### Method 2: Activate Script Activation
- Obtain the required machine code for activation, enter the sbin directory of
the installation directory, and execute the activation script:
@@ -150,16 +206,15 @@ License has been stored to sbin/../activation/license
Import completed. Please start cluster and excute 'show cluster' to verify
activation status
```
-### 5、Start DataNode
+#### 4.3 Start DataNode
Enter the sbin directory of iotdb and start datanode:
```shell
-cd sbin
./start-datanode.sh -d # The "- d" parameter will start in the background
```
-### 6、Verify Deployment
+### 5、Verify Deployment
Can be executed directly/ Cli startup script in sbin directory:
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 3e9d7748..0dff43d1 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
@@ -159,15 +159,9 @@ On each server, navigate to the `sbin` directory and start
the DataNode:
### 3.6 Activate the Database
-#### Option 1: File-Based Activation
+#### Option 1: Command-Based Activation
-1. Start all ConfigNodes and DataNodes.
-2. Copy the `system_info` file from the `activation` directory on each server
and send them to the Timecho team.
-3. Place the license files provided by the Timecho team into the corresponding
`activation` folder for each node.
-
-#### Option 2: Command-Based Activation
-
-1. Enter the IoTDB CLI for each node:
+1. Enter the IoTDB CLI on any node of the cluster:
- **For Table Model**:
```SQL
# For Linux or macOS
@@ -177,21 +171,13 @@ On each server, navigate to the `sbin` directory and
start the DataNode:
./start-cli.bat -sql_dialect table
```
- - **For Tree Model**:
- ```SQL
- # For Linux or macOS
- ./start-cli.sh
-
- # For Windows
- ./start-cli.bat
- ```
2. Run the following command to retrieve the machine code required for
activation:
```Bash
show system info
```
-3. Copy the returned machine code of each server (displayed as a green string)
and send it to the Timecho team:
+3. Copy the returned machine codes of all nodes in the cluster (displayed as a
green string) and send it to the Timecho team:
```Bash
+--------------------------------------------------------------+
@@ -209,6 +195,14 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,0
[...]
```
+
+#### Option 2: File-Based Activation
+
+1. Start all ConfigNodes and DataNodes.
+2. Copy the `system_info` file from the `activation` directory on each server
and send them to the Timecho team.
+3. Place the license files provided by the Timecho team into the corresponding
`activation` folder for each node.
+
+
### 3.7 Verify Activation
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the
database has been successfully activated.
diff --git
a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 79c1d802..1f93341e 100644
---
a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -126,14 +126,7 @@ Navigate to the `sbin` directory of IoTDB and start the
DataNode:
### 2.5 Activate the Database
-#### Option 1: File-Based Activation
-
-- Start both the ConfigNode and DataNode.
-- Navigate to the `activation` folder and copy the `system_info` file.
-- Send the `system_info` file to the Timecho team.
-- Place the license file provided by the Timecho team into the corresponding
`activation` folder for each node.
-
-#### Option 2: Command-Based Activation
+#### Option 1: Command-Based Activation
1. Enter the IoTDB CLI.
- **For Table Model**:
@@ -145,14 +138,6 @@ Navigate to the `sbin` directory of IoTDB and start the
DataNode:
./start-cli.bat -sql_dialect table
```
- - **For Tree Model**:
- - ```SQL
- # For Linux or macOS
- ./start-cli.sh
-
- # For Windows
- ./start-cli.bat
- ```
2. Run the following command to retrieve the machine code required for
activation:
```Bash
@@ -177,6 +162,14 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
```
+#### Option 2: File-Based Activation
+
+- Start both the ConfigNode and DataNode.
+- Navigate to the `activation` folder and copy the `system_info` file.
+- Send the `system_info` file to the Timecho team.
+- Place the license file provided by the Timecho team into the corresponding
`activation` folder for each node.
+
+
### 2.6 Verify Activation
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the
database has been successfully activated.
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 c5fbcb13..3e4bfa8d 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
@@ -161,25 +161,9 @@ cd sbin
### 3.6 Activate Database
-#### Option 1: File-Based Activation
+#### Option 1: Command-Based Activation
-1. Start all ConfigNodes and DataNodes.
-2. Copy the `system_info` file from the `activation` directory on each server
and send them to the Timecho team.
-3. Place the license files provided by the Timecho team into the corresponding
`activation` folder for each node.
-
-#### Option 2: Command-Based Activation
-
-1. Enter the IoTDB CLI for each node:
-
-- **For Table Model**:
-
- ```SQL
- # For Linux or macOS
- ./start-cli.sh -sql_dialect table
-
- # For Windows
- ./start-cli.bat -sql_dialect table
- ```
+1. Enter the IoTDB CLI on any node of the cluster:
- **For Tree Model**:
@@ -197,7 +181,7 @@ cd sbin
show system info
```
-3. Copy the returned machine code of each server (displayed as a green string)
and send it to the Timecho team:
+3. Copy the returned machine codes of all nodes in the cluster (displayed as a
green string) and send it to the Timecho team:
```Bash
+--------------------------------------------------------------+
@@ -215,6 +199,14 @@ cd sbin
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
```
+
+#### Option 2: File-Based Activation
+
+1. Start all ConfigNodes and DataNodes.
+2. Copy the `system_info` file from the `activation` directory on each server
and send them to the Timecho team.
+3. Place the license files provided by the Timecho team into the corresponding
`activation` folder for each node.
+
+
### 3.7 Verify Activation
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the
database has been successfully activated.
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 6c454ce5..5bbbb64d 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -124,27 +124,10 @@ Navigate to the `sbin` directory of IoTDB and start the
DataNode:
### 2.5 Activate Database
-#### Option 1: File-Based Activation
-
-1. Start both the ConfigNode and DataNode.
-2. Navigate to the `activation` folder and copy the `system_info` file.
-3. Send the `system_info` file to the Timecho team.
-4. Place the license file provided by the Timecho team into the corresponding
`activation` folder for each node.
-
-#### Option 2: Command-Based Activation
+#### Option 1: Command-Based Activation
1. Enter the IoTDB CLI.
-- **For Table Model**:
-
-```SQL
-# For Linux or macOS
-./start-cli.sh -sql_dialect table
-
-# For Windows
-./start-cli.bat -sql_dialect table
-```
-
- **For Tree Model**:
```SQL
@@ -173,6 +156,15 @@ Total line number = 1
It costs 0.030s
```
+
+#### Option 2: File-Based Activation
+
+1. Start both the ConfigNode and DataNode.
+2. Navigate to the `activation` folder and copy the `system_info` file.
+3. Send the `system_info` file to the Timecho team.
+4. Place the license file provided by the Timecho team into the corresponding
`activation` folder for each node.
+
+
4. Enter the activation code provided by the Timecho team in the CLI using the
following format. Wrap the activation code in single quotes ('):
```Bash
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 50e59743..d7f91fe9 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
@@ -156,14 +156,9 @@ cd sbin
### 3.5 激活数据库
-#### 方式一：激活文件拷贝激活
+#### 方式一：通过 CLI 激活
-- 依次启动3个Confignode、Datanode节点后，每台机器各自的activation文件夹,
分别拷贝每台机器的system_info文件给天谋工作人员;
-- 工作人员将返回每个ConfigNode、Datanode节点的license文件，这里会返回3个license文件；
-- 将3个license文件分别放入对应的ConfigNode节点的activation文件夹下；
-
-#### 方式二：激活脚本激活
-- 依次获取3台机器的机器码，进入 IoTDB CLI
+- 进入集群任一节点 CLI，执行获取机器码的语句
- 表模型 CLI 进入命令：
@@ -175,23 +170,13 @@ cd sbin
./start-cli.bat -sql_dialect table
```
- - 树模型 CLI 进入命令：
-
- ```SQL
- # Linux或MACOS系统
- ./start-cli.sh
-
- # windows系统
- ./start-cli.bat
- ```
-
- 执行以下内容获取激活所需机器码：
```Bash
show system info
```
- - 显示如下信息，这里显示的是1台机器的机器码 ：
+ - 系统将自动返回集群所有节点的机器码
```Bash
+--------------------------------------------------------------+
@@ -203,16 +188,24 @@ cd sbin
It costs 0.030s
```
-- 其他2个节点依次进入到IoTDB树模型的CLI中，执行语句后将获取的3台机器的机器码都复制给天谋工作人员
+- 将获取的机器码复制给天谋工作人员
-- 工作人员会返回3段激活码，正常是与提供的3个机器码的顺序对应的，请分别将各自的激活码粘贴到CLI中，如下提示：
+- 工作人员会返回激活码，正常是与提供的机器码的顺序对应的，请将整串激活码粘贴到CLI中进行激活
- - 注：激活码前后需要用`'`符号进行标注，如所示
+ - 注：激活码前后需要用`'`符号进行标注，如下所示
```Bash
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
```
+
+#### 方式二：激活文件拷贝激活
+
+- 依次启动3个Confignode、Datanode节点后，每台机器各自的activation文件夹,
分别拷贝每台机器的system_info文件给天谋工作人员;
+- 工作人员将返回每个ConfigNode、Datanode节点的license文件，这里会返回3个license文件；
+- 将3个license文件分别放入对应的ConfigNode节点的activation文件夹下；
+
+
### 3.6 验证激活
当看到“Result”字段状态显示为success表示激活成功
diff --git
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 17790acf..4afc00b5 100644
---
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -119,14 +119,10 @@ DataNode 配置
### 2.5 激活数据库
-#### 方式一：文件激活
+#### 方式一：命令激活
-- 启动Confignode、Datanode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
-- 收到工作人员返回的 license文件
-- 将license文件放入对应节点的activation文件夹下；
-
-#### 方式二：命令激活
- 进入 IoTDB CLI
+
- 表模型 CLI 进入命令：
```SQL
# Linux或MACOS系统
@@ -136,14 +132,6 @@ DataNode 配置
./start-cli.bat -sql_dialect table
```
- - 树模型 CLI 进入命令：
- ```SQL
- # Linux或MACOS系统
- ./start-cli.sh
-
- # windows系统
- ./start-cli.bat
- ```
- 执行以下内容获取激活所需机器码：
```Bash
@@ -169,6 +157,14 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
```
+
+#### 方式二：文件激活
+
+- 启动Confignode、Datanode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
+- 收到工作人员返回的 license文件
+- 将license文件放入对应节点的activation文件夹下；
+
+
### 2.6 验证激活
当看到“ClusterActivationStatus”字段状态显示为ACTIVATED表示激活成功
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 3bef355d..7b86f17e 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
@@ -156,24 +156,9 @@ cd sbin
### 3.5 激活数据库
-#### 方式一：激活文件拷贝激活
+#### 方式一：通过 CLI 激活
-- 依次启动3个Confignode、Datanode节点后，每台机器各自的activation文件夹,
分别拷贝每台机器的system_info文件给天谋工作人员;
-- 工作人员将返回每个ConfigNode、Datanode节点的license文件，这里会返回3个license文件；
-- 将3个license文件分别放入对应的ConfigNode节点的activation文件夹下；
-
-#### 方式二：激活脚本激活
-- 依次获取3台机器的机器码，进入 IoTDB CLI
-
- - 表模型 CLI 进入命令：
-
- ```SQL
- # Linux或MACOS系统
- ./start-cli.sh -sql_dialect table
-
- # windows系统
- ./start-cli.bat -sql_dialect table
- ```
+- 进入集群任一节点 CLI，执行获取机器码的语句
- 树模型 CLI 进入命令：
@@ -191,7 +176,7 @@ cd sbin
show system info
```
- - 显示如下信息，这里显示的是1台机器的机器码 ：
+ - 系统将自动返回集群所有节点的机器码
```Bash
+--------------------------------------------------------------+
@@ -203,16 +188,24 @@ cd sbin
It costs 0.030s
```
-- 其他2个节点依次进入到IoTDB树模型的CLI中，执行语句后将获取的3台机器的机器码都复制给天谋工作人员
+- 将获取的机器码复制给天谋工作人员
-- 工作人员会返回3段激活码，正常是与提供的3个机器码的顺序对应的，请分别将各自的激活码粘贴到CLI中，如下提示：
+- 工作人员会返回激活码，正常是与提供的机器码的顺序对应的，请将整串激活码粘贴到CLI中进行激活
- - 注：激活码前后需要用`'`符号进行标注，如所示
+ - 注：激活码前后需要用`'`符号进行标注，如下所示
```Bash
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
```
+
+#### 方式二：激活文件拷贝激活
+
+- 依次启动3个Confignode、Datanode节点后，每台机器各自的activation文件夹,
分别拷贝每台机器的system_info文件给天谋工作人员;
+- 工作人员将返回每个ConfigNode、Datanode节点的license文件，这里会返回3个license文件；
+- 将3个license文件分别放入对应的ConfigNode节点的activation文件夹下；
+
+
### 3.6 验证激活
当看到“Result”字段状态显示为success表示激活成功
diff --git
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index cc677aae..3bbe5f0b 100644
---
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -127,23 +127,9 @@ cd iotdb-enterprise-{version}-bin
### 2.5 激活数据库
-#### 方式一：文件激活
-
-- 启动Confignode、Datanode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
-- 收到工作人员返回的 license文件
-- 将license文件放入对应节点的activation文件夹下；
-
-#### 方式二：命令激活
+#### 方式一：命令激活
- 进入 IoTDB CLI
- - 表模型 CLI 进入命令：
- ```SQL
- # Linux或MACOS系统
- ./start-cli.sh -sql_dialect table
-
- # windows系统
- ./start-cli.bat -sql_dialect table
- ```
-
+
- 树模型 CLI 进入命令：
```SQL
# Linux或MACOS系统
@@ -177,6 +163,14 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
```
+#### 方式二：文件激活
+
+- 启动Confignode、Datanode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
+- 收到工作人员返回的 license文件
+- 将license文件放入对应节点的activation文件夹下；
+
+
+
### 2.6 验证激活
当看到“ClusterActivationStatus”字段状态显示为ACTIVATED表示激活成功
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 790f2244..5de09125 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
@@ -134,30 +134,84 @@ cd iotdb-enterprise-{version}-bin
> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
-### 启动ConfigNode节点
+### 启动及激活数据库 （V 1.3.4 及以后的 1.x 版本）
+
+#### 启动 ConfigNode 节点
+
+先启动第一个iotdb-1的confignode, 保证种子confignode节点先启动，然后依次启动第2和第3个confignode节点
+
+```Bash
+./start-confignode.sh -d #“-d”参数将在后台进行启动
+```
+如果启动失败，请参考[常见问题](#常见问题)。
+
+#### 启动 DataNode 节点
+
+分别进入iotdb的`sbin`目录下，依次启动3个datanode节点：
+
+```Bash
+./start-datanode.sh -d #-d参数将在后台进行启动
+```
+
+#### 激活数据库
+
+##### 通过 CLI 激活
+
+- 进入集群任一节点 CLI，执行获取机器码的语句
+
+ ```SQL
+ -- 连接CLI
+ ./sbin/start-cli.sh
+ -- 获取激活所需机器码
+ IoTDB> show system info
+```
+
+- 系统将自动返回集群所有节点的机器码
+
+```Bash
++--------------------------------------------------------------+
+| SystemInfo|
++--------------------------------------------------------------+
+|01-TE5NLES4-UDDWCMYE,01-GG5NLES4-XXDWCMYE,01-FF5NLES4-WWWWCMYE|
++--------------------------------------------------------------+
+Total line number = 1
+It costs 0.030s
+```
+
+- 将获取的机器码复制给天谋工作人员
+
+- 工作人员会返回激活码，正常是与提供的机器码的顺序对应的，请将整串激活码粘贴到CLI中进行激活
+
+ - 注：激活码前后需要用`'`符号进行标注，如下所示
+
+ ```Bash
+ IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
+ ```
+
+### 启动及激活数据库 （V 1.3.4 之前版本）
+
+#### 启动 ConfigNode 节点
先启动第一个iotdb-1的confignode, 保证种子confignode节点先启动，然后依次启动第2和第3个confignode节点
```Bash
-cd sbin
./start-confignode.sh -d #“-d”参数将在后台进行启动
```
如果启动失败，请参考[常见问题](#常见问题)。
-### 激活数据库
+#### 激活数据库
-#### **方式一：激活文件拷贝激活**
+##### 方式一：激活文件拷贝激活
- 依次启动3个confignode节点后，每台机器各自的`activation`文件夹, 分别拷贝每台机器的`system_info`文件给天谋工作人员;
- 工作人员将返回每个ConfigNode节点的license文件，这里会返回3个license文件；
- 将3个license文件分别放入对应的ConfigNode节点的`activation`文件夹下；
-#### 方式二：激活脚本激活
+##### 方式二：激活脚本激活
- 依次获取3台机器的机器码，分别进入安装目录的`sbin`目录，执行激活脚本`start-activate.sh`:
```Bash
- cd sbin
./start-activate.sh
```
@@ -179,12 +233,11 @@ cd sbin
Import completed. Please start cluster and excute 'show cluster' to verify
activation status
```
-### 启动DataNode 节点
+#### 启动 DataNode 节点
分别进入iotdb的`sbin`目录下，依次启动3个datanode节点：
-```Go
-cd sbin
+```Bash
./start-datanode.sh -d #-d参数将在后台进行启动
```
diff --git
a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 20267781..7c0d5664 100644
---
a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -107,7 +107,62 @@ cd iotdb-enterprise-{version}-bin
> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
-### 启动 ConfigNode 节点
+### 启动及激活数据库 （V 1.3.4 及以后的 1.x 版本）
+
+#### 启动 ConfigNode 节点
+
+进入iotdb的sbin目录下，启动confignode
+
+```shell
+./start-confignode.sh -d #“-d”参数将在后台进行启动
+```
+如果启动失败，请参考[常见问题](#常见问题)。
+
+#### 启动 DataNode 节点
+
+进入iotdb的sbin目录下，启动datanode：
+
+```shell
+./start-datanode.sh -d #-d参数将在后台进行启动
+```
+
+#### 激活数据库
+
+##### 通过 CLI 激活
+
+- 进入 CLI
+
+ ```SQL
+ ./sbin/start-cli.sh
+```
+
+- 执行以下内容获取激活所需机器码：
+
+ ```Bash
+ show system info
+ ```
+
+- 将返回机器码（即绿色字符串）复制给天谋工作人员：
+
+```Bash
++--------------------------------------------------------------+
+| SystemInfo|
++--------------------------------------------------------------+
+| 01-TE5NLES4-UDDWCMYE|
++--------------------------------------------------------------+
+Total line number = 1
+It costs 0.030s
+```
+
+- 将工作人员返回的激活码输入到CLI中，输入以下内容
+ - 注：激活码前后需要用`'`符号进行标注，如所示
+
+```Bash
+IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
+```
+### 启动及激活数据库 （V 1.3.4 之前版本）
+
+#### 启动 ConfigNode 节点
进入iotdb的sbin目录下，启动confignode
@@ -116,15 +171,15 @@ cd iotdb-enterprise-{version}-bin
```
如果启动失败，请参考[常见问题](#常见问题)。
-### 激活数据库
+#### 激活数据库
-#### 方式一：激活文件拷贝激活
+##### 方式一：激活文件拷贝激活
- 启动confignode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
- 收到工作人员返回的 license文件
- 将license文件放入对应节点的activation文件夹下；
-#### 方式二：激活脚本激活
+##### 方式二：激活脚本激活
- 获取激活所需机器码，进入安装目录的sbin目录，执行激活脚本:
@@ -150,15 +205,15 @@ License has been stored to sbin/../activation/license
Import completed. Please start cluster and excute 'show cluster' to verify
activation status
```
-### 启动DataNode 节点
+#### 启动 DataNode 节点
进入iotdb的sbin目录下，启动datanode：
```shell
-cd sbin
./start-datanode.sh -d #-d参数将在后台进行启动
```
+
### 验证部署
可直接执行 ./sbin 目录下的 Cli 启动脚本：
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 cfe139ab..5de09125 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
@@ -134,30 +134,84 @@ cd iotdb-enterprise-{version}-bin
> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
-### 启动ConfigNode节点
+### 启动及激活数据库 （V 1.3.4 及以后的 1.x 版本）
+
+#### 启动 ConfigNode 节点
先启动第一个iotdb-1的confignode, 保证种子confignode节点先启动，然后依次启动第2和第3个confignode节点
```Bash
-cd sbin
./start-confignode.sh -d #“-d”参数将在后台进行启动
```
如果启动失败，请参考[常见问题](#常见问题)。
-### 激活数据库
+#### 启动 DataNode 节点
+
+分别进入iotdb的`sbin`目录下，依次启动3个datanode节点：
+
+```Bash
+./start-datanode.sh -d #-d参数将在后台进行启动
+```
+
+#### 激活数据库
+
+##### 通过 CLI 激活
+
+- 进入集群任一节点 CLI，执行获取机器码的语句
+
+ ```SQL
+ -- 连接CLI
+ ./sbin/start-cli.sh
+ -- 获取激活所需机器码
+ IoTDB> show system info
+```
+
+- 系统将自动返回集群所有节点的机器码
+
+```Bash
++--------------------------------------------------------------+
+| SystemInfo|
++--------------------------------------------------------------+
+|01-TE5NLES4-UDDWCMYE,01-GG5NLES4-XXDWCMYE,01-FF5NLES4-WWWWCMYE|
++--------------------------------------------------------------+
+Total line number = 1
+It costs 0.030s
+```
+
+- 将获取的机器码复制给天谋工作人员
+
+- 工作人员会返回激活码，正常是与提供的机器码的顺序对应的，请将整串激活码粘贴到CLI中进行激活
-#### **方式一：激活文件拷贝激活**
+ - 注：激活码前后需要用`'`符号进行标注，如下所示
+
+ ```Bash
+ IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
+ ```
+
+### 启动及激活数据库 （V 1.3.4 之前版本）
+
+#### 启动 ConfigNode 节点
+
+先启动第一个iotdb-1的confignode, 保证种子confignode节点先启动，然后依次启动第2和第3个confignode节点
+
+```Bash
+./start-confignode.sh -d #“-d”参数将在后台进行启动
+```
+如果启动失败，请参考[常见问题](#常见问题)。
+
+#### 激活数据库
+
+##### 方式一：激活文件拷贝激活
- 依次启动3个confignode节点后，每台机器各自的`activation`文件夹, 分别拷贝每台机器的`system_info`文件给天谋工作人员;
- 工作人员将返回每个ConfigNode节点的license文件，这里会返回3个license文件；
- 将3个license文件分别放入对应的ConfigNode节点的`activation`文件夹下；
-#### 方式二：激活脚本激活
+##### 方式二：激活脚本激活
- 依次获取3台机器的机器码，分别进入安装目录的`sbin`目录，执行激活脚本`start-activate.sh`:
```Bash
- cd sbin
./start-activate.sh
```
@@ -179,12 +233,11 @@ cd sbin
Import completed. Please start cluster and excute 'show cluster' to verify
activation status
```
-### 启动DataNode 节点
+#### 启动 DataNode 节点
分别进入iotdb的`sbin`目录下，依次启动3个datanode节点：
-```Go
-cd sbin
+```Bash
./start-datanode.sh -d #-d参数将在后台进行启动
```
@@ -322,7 +375,7 @@ sbin/start-confignode.bat
#### 移除ConfigNode节点
-首先通过CLI连接集群，通过`show confignodes`确认想要移除ConfigNode的NodeID：
+首先通过CLI连接集群，通过`show confignodes`确认想要移除ConfigNode的内部地址与端口号：
```Bash
IoTDB> show confignodes
@@ -337,9 +390,15 @@ Total line number = 3
It costs 0.030s
```
-然后使用SQL将ConfigNode移除，SQL命令：
+然后使用脚本将ConfigNode移除。脚本命令：
+
```Bash
-remove confignode [confignode_id]
+# Linux / MacOS
+sbin/remove-confignode.sh [confignode_id]
+
+#Windows
+sbin/remove-confignode.bat [confignode_id]
+
```
### DataNode节点维护
@@ -385,7 +444,7 @@ sbin/start-datanode.bat
#### 移除DataNode节点
-首先通过CLI连接集群，通过`show datanodes`确认想要移除的DataNode的NodeID：
+首先通过CLI连接集群，通过`show datanodes`确认想要移除的DataNode的RPC地址与端口号：
```Bash
IoTDB> show datanodes
@@ -400,9 +459,14 @@ Total line number = 3
It costs 0.110s
```
-然后使用SQL将DataNode移除，SQL命令：
+然后使用脚本将DataNode移除。脚本命令：
+
```Bash
-remove datanode [datanode_id]
+# Linux / MacOS
+sbin/remove-datanode.sh [datanode_id]
+
+#Windows
+sbin/remove-datanode.bat [datanode_id]
```
## 常见问题
diff --git
a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 20267781..7c0d5664 100644
---
a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -107,7 +107,62 @@ cd iotdb-enterprise-{version}-bin
> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
-### 启动 ConfigNode 节点
+### 启动及激活数据库 （V 1.3.4 及以后的 1.x 版本）
+
+#### 启动 ConfigNode 节点
+
+进入iotdb的sbin目录下，启动confignode
+
+```shell
+./start-confignode.sh -d #“-d”参数将在后台进行启动
+```
+如果启动失败，请参考[常见问题](#常见问题)。
+
+#### 启动 DataNode 节点
+
+进入iotdb的sbin目录下，启动datanode：
+
+```shell
+./start-datanode.sh -d #-d参数将在后台进行启动
+```
+
+#### 激活数据库
+
+##### 通过 CLI 激活
+
+- 进入 CLI
+
+ ```SQL
+ ./sbin/start-cli.sh
+```
+
+- 执行以下内容获取激活所需机器码：
+
+ ```Bash
+ show system info
+ ```
+
+- 将返回机器码（即绿色字符串）复制给天谋工作人员：
+
+```Bash
++--------------------------------------------------------------+
+| SystemInfo|
++--------------------------------------------------------------+
+| 01-TE5NLES4-UDDWCMYE|
++--------------------------------------------------------------+
+Total line number = 1
+It costs 0.030s
+```
+
+- 将工作人员返回的激活码输入到CLI中，输入以下内容
+ - 注：激活码前后需要用`'`符号进行标注，如所示
+
+```Bash
+IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
+```
+### 启动及激活数据库 （V 1.3.4 之前版本）
+
+#### 启动 ConfigNode 节点
进入iotdb的sbin目录下，启动confignode
@@ -116,15 +171,15 @@ cd iotdb-enterprise-{version}-bin
```
如果启动失败，请参考[常见问题](#常见问题)。
-### 激活数据库
+#### 激活数据库
-#### 方式一：激活文件拷贝激活
+##### 方式一：激活文件拷贝激活
- 启动confignode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
- 收到工作人员返回的 license文件
- 将license文件放入对应节点的activation文件夹下；
-#### 方式二：激活脚本激活
+##### 方式二：激活脚本激活
- 获取激活所需机器码，进入安装目录的sbin目录，执行激活脚本:
@@ -150,15 +205,15 @@ License has been stored to sbin/../activation/license
Import completed. Please start cluster and excute 'show cluster' to verify
activation status
```
-### 启动DataNode 节点
+#### 启动 DataNode 节点
进入iotdb的sbin目录下，启动datanode：
```shell
-cd sbin
./start-datanode.sh -d #-d参数将在后台进行启动
```
+
### 验证部署
可直接执行 ./sbin 目录下的 Cli 启动脚本：
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 8f116f1e..3ac4e5d7 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
@@ -156,14 +156,9 @@ cd sbin
### 3.5 激活数据库
-#### 方式一：激活文件拷贝激活
+#### 方式一：通过 CLI 激活
-- 依次启动3个Confignode、Datanode节点后，每台机器各自的activation文件夹,
分别拷贝每台机器的system_info文件给天谋工作人员;
-- 工作人员将返回每个ConfigNode、Datanode节点的license文件，这里会返回3个license文件；
-- 将3个license文件分别放入对应的ConfigNode节点的activation文件夹下；
-
-#### 方式二：激活脚本激活
-- 依次获取3台机器的机器码，进入 IoTDB CLI
+- 进入集群任一节点 CLI，执行获取机器码的语句
- 表模型 CLI 进入命令：
@@ -175,23 +170,13 @@ cd sbin
./start-cli.bat -sql_dialect table
```
- - 树模型 CLI 进入命令：
-
- ```SQL
- # Linux或MACOS系统
- ./start-cli.sh
-
- # windows系统
- ./start-cli.bat
- ```
-
- 执行以下内容获取激活所需机器码：
```Bash
show system info
```
- - 显示如下信息，这里显示的是1台机器的机器码 ：
+ - 系统将自动返回集群所有节点的机器码
```Bash
+--------------------------------------------------------------+
@@ -203,16 +188,24 @@ cd sbin
It costs 0.030s
```
-- 其他2个节点依次进入到IoTDB树模型的CLI中，执行语句后将获取的3台机器的机器码都复制给天谋工作人员
+- 将获取的机器码复制给天谋工作人员
-- 工作人员会返回3段激活码，正常是与提供的3个机器码的顺序对应的，请分别将各自的激活码粘贴到CLI中，如下提示：
+- 工作人员会返回激活码，正常是与提供的机器码的顺序对应的，请将整串激活码粘贴到CLI中进行激活
- - 注：激活码前后需要用`'`符号进行标注，如所示
+ - 注：激活码前后需要用`'`符号进行标注，如下所示
```Bash
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
```
+
+#### 方式二：激活文件拷贝激活
+
+- 依次启动3个Confignode、Datanode节点后，每台机器各自的activation文件夹,
分别拷贝每台机器的system_info文件给天谋工作人员;
+- 工作人员将返回每个ConfigNode、Datanode节点的license文件，这里会返回3个license文件；
+- 将3个license文件分别放入对应的ConfigNode节点的activation文件夹下；
+
+
### 3.6 验证激活
当看到“Result”字段状态显示为success表示激活成功
diff --git
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 55813c0c..c6cd4808 100644
---
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -119,14 +119,10 @@ DataNode 配置
### 2.5 激活数据库
-#### 方式一：文件激活
+#### 方式一：命令激活
-- 启动Confignode、Datanode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
-- 收到工作人员返回的 license文件
-- 将license文件放入对应节点的activation文件夹下；
-
-#### 方式二：命令激活
- 进入 IoTDB CLI
+
- 表模型 CLI 进入命令：
```SQL
# Linux或MACOS系统
@@ -136,14 +132,6 @@ DataNode 配置
./start-cli.bat -sql_dialect table
```
- - 树模型 CLI 进入命令：
- ```SQL
- # Linux或MACOS系统
- ./start-cli.sh
-
- # windows系统
- ./start-cli.bat
- ```
- 执行以下内容获取激活所需机器码：
```Bash
@@ -169,6 +157,14 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
```
+
+#### 方式二：文件激活
+
+- 启动Confignode、Datanode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
+- 收到工作人员返回的 license文件
+- 将license文件放入对应节点的activation文件夹下；
+
+
### 2.6 验证激活
当看到“ClusterActivationStatus”字段状态显示为ACTIVATED表示激活成功
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 3bef355d..07b9c2f5 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
@@ -156,24 +156,9 @@ cd sbin
### 3.5 激活数据库
-#### 方式一：激活文件拷贝激活
+#### 方式一：通过 CLI 激活
-- 依次启动3个Confignode、Datanode节点后，每台机器各自的activation文件夹,
分别拷贝每台机器的system_info文件给天谋工作人员;
-- 工作人员将返回每个ConfigNode、Datanode节点的license文件，这里会返回3个license文件；
-- 将3个license文件分别放入对应的ConfigNode节点的activation文件夹下；
-
-#### 方式二：激活脚本激活
-- 依次获取3台机器的机器码，进入 IoTDB CLI
-
- - 表模型 CLI 进入命令：
-
- ```SQL
- # Linux或MACOS系统
- ./start-cli.sh -sql_dialect table
-
- # windows系统
- ./start-cli.bat -sql_dialect table
- ```
+- 进入集群任一节点 CLI，执行获取机器码的语句
- 树模型 CLI 进入命令：
@@ -191,7 +176,7 @@ cd sbin
show system info
```
- - 显示如下信息，这里显示的是1台机器的机器码 ：
+ - 系统将自动返回集群所有节点的机器码
```Bash
+--------------------------------------------------------------+
@@ -203,16 +188,24 @@ cd sbin
It costs 0.030s
```
-- 其他2个节点依次进入到IoTDB树模型的CLI中，执行语句后将获取的3台机器的机器码都复制给天谋工作人员
+- 将获取的机器码复制给天谋工作人员
-- 工作人员会返回3段激活码，正常是与提供的3个机器码的顺序对应的，请分别将各自的激活码粘贴到CLI中，如下提示：
+- 工作人员会返回激活码，正常是与提供的机器码的顺序对应的，请将整串激活码粘贴到CLI中进行激活
- - 注：激活码前后需要用`'`符号进行标注，如所示
+ - 注：激活码前后需要用`'`符号进行标注，如下所示
```Bash
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA===,01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA=
[...]
```
+
+#### 方式二：激活文件拷贝激活
+
+- 依次启动3个Confignode、Datanode节点后，每台机器各自的activation文件夹,
分别拷贝每台机器的system_info文件给天谋工作人员;
+- 工作人员将返回每个ConfigNode、Datanode节点的license文件，这里会返回3个license文件；
+- 将3个license文件分别放入对应的ConfigNode节点的activation文件夹下；
+
+
### 3.6 验证激活
当看到“Result”字段状态显示为success表示激活成功
diff --git
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index cc677aae..5cd25706 100644
---
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -127,22 +127,8 @@ cd iotdb-enterprise-{version}-bin
### 2.5 激活数据库
-#### 方式一：文件激活
-
-- 启动Confignode、Datanode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
-- 收到工作人员返回的 license文件
-- 将license文件放入对应节点的activation文件夹下；
-
-#### 方式二：命令激活
+#### 方式一：命令激活
- 进入 IoTDB CLI
- - 表模型 CLI 进入命令：
- ```SQL
- # Linux或MACOS系统
- ./start-cli.sh -sql_dialect table
-
- # windows系统
- ./start-cli.bat -sql_dialect table
- ```
- 树模型 CLI 进入命令：
```SQL
@@ -177,6 +163,14 @@ It costs 0.030s
IoTDB> activate
'01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
```
+
+#### 方式二：文件激活
+
+- 启动Confignode、Datanode节点后，进入activation文件夹, 将 system_info文件复制给天谋工作人员
+- 收到工作人员返回的 license文件
+- 将license文件放入对应节点的activation文件夹下；
+
+
### 2.6 验证激活
当看到“ClusterActivationStatus”字段状态显示为ACTIVATED表示激活成功
