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 914354ac1..e0b008b7d 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 @@ -206,9 +206,22 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 3.7 Verify Activation -Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. +In the CLI, you can check the activation status by running the `show activation` command; the example below shows a status of ACTIVATED, indicating successful activation. + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` -![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) ### 3.8 One-click Cluster Start and Stop 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 41fca6793..cec93ce37 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 @@ -173,7 +173,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 2.6 Verify Activation -Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. +In the CLI, you can check the activation status by running the `show activation` command. Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. ![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png) 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 12058f850..ef2431e57 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 @@ -209,9 +209,22 @@ cd sbin ### 3.7 Verify Activation -Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. +In the CLI, you can check the activation status by running the `show activation` command; the example below shows a status of ACTIVATED, indicating successful activation. + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` -![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) ### 3.8 One-click Cluster Start and Stop 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 3a87d4ede..8ffd44bbb 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 @@ -173,7 +173,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 2.6 Verify Activation -Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. +In the CLI, you can check the activation status by running the `show activation` command. Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. ![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png) 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 9f4178451..7633b7bfb 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 @@ -266,6 +266,22 @@ When you see the display of `Activated` on the far right, it indicates successfu ![](/img/%E4%BC%81%E4%B8%9A%E7%89%88%E6%BF%80%E6%B4%BB.png) +In the CLI, you can also check the activation status by running the `show activation` command; the example below shows a status of ACTIVATED, indicating successful activation. + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` + > 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. 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 24e383c7c..6273f6fe9 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 @@ -232,6 +232,22 @@ When you see the display "Activated" on the far right, it indicates successful a ![](/img/show%20cluster.png) +In the CLI, you can also check the activation status by running the `show activation` command; the example below shows a status of ACTIVATED, indicating successful activation. + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` + > The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). 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. 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 9f4178451..7633b7bfb 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 @@ -266,6 +266,22 @@ When you see the display of `Activated` on the far right, it indicates successfu ![](/img/%E4%BC%81%E4%B8%9A%E7%89%88%E6%BF%80%E6%B4%BB.png) +In the CLI, you can also check the activation status by running the `show activation` command; the example below shows a status of ACTIVATED, indicating successful activation. + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` + > 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. 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 24e383c7c..d72228749 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 @@ -232,6 +232,21 @@ When you see the display "Activated" on the far right, it indicates successful a ![](/img/show%20cluster.png) +In the CLI, you can also check the activation status by running the `show activation` command; the example below shows a status of ACTIVATED, indicating successful activation. + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` > The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). 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. 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 db3fb62c7..e50114a15 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 @@ -205,9 +205,22 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 3.7 Verify Activation -Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. +In the CLI, you can check the activation status by running the `show activation` command; the example below shows a status of ACTIVATED, indicating successful activation. + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` -![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) ### 3.8 One-click Cluster Start and Stop 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 c733ce4ed..cebe6307b 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 @@ -172,7 +172,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 2.6 Verify Activation -Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. +In the CLI, you can check the activation status by running the `show activation` command. Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. ![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png) 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 e3c8482e6..85d9c3f21 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md @@ -209,9 +209,22 @@ cd sbin ### 3.7 Verify Activation -Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. +In the CLI, you can check the activation status by running the `show activation` command; the example below shows a status of ACTIVATED, indicating successful activation. + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` -![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) ### 3.8 One-click Cluster Start and Stop 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 a48ed2d73..63a8ecdab 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 @@ -173,7 +173,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 2.6 Verify Activation -Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. +In the CLI, you can check the activation status by running the `show activation` command. Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated. ![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png) 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 2b803ad2c..d44dc3b96 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 @@ -208,10 +208,21 @@ cd sbin ### 3.6 验证激活 -当看到“Result”字段状态显示为success表示激活成功 - -![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) - +可在 CLI 中通过执行 `show activation` 命令查看激活状态，示例如下，状态显示为 ACTIVATED 表示激活成功 + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` ### 3.7 一键启停集群 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 659c5180a..a0ceda68e 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 @@ -167,9 +167,10 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 2.6 验证激活 -当看到“ClusterActivationStatus”字段状态显示为ACTIVATED表示激活成功 +可在 CLI 中通过执行 `show activation` 命令查看激活状态，当看到“ClusterActivationStatus”字段状态显示为 ACTIVATED 表示激活成功 ![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png) + ## 3. 常见问题 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 d056450a0..8cfdd2374 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,9 +208,21 @@ cd sbin ### 3.6 验证激活 -当看到“Result”字段状态显示为success表示激活成功 - -![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) +可在 CLI 中通过执行 `show activation` 命令查看激活状态，示例如下，状态显示为 ACTIVATED 表示激活成功 + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` ### 3.7 一键启停集群 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 4afa4a4f5..3719d01b1 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 @@ -173,10 +173,11 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 2.6 验证激活 -当看到“ClusterActivationStatus”字段状态显示为ACTIVATED表示激活成功 +可在 CLI 中通过执行 `show activation` 命令查看激活状态，当看到“ClusterActivationStatus”字段状态显示为 ACTIVATED 表示激活成功 ![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png) + ## 3. 常见问题 1. 部署过程中多次提示激活失败 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 b151c5efd..e3396576c 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 @@ -259,6 +259,23 @@ It costs 0.030s ![](/img/%E4%BC%81%E4%B8%9A%E7%89%88%E6%BF%80%E6%B4%BB.png) +还可在 CLI 中通过执行 `show activation` 命令查看激活状态，示例如下，状态显示为ACTIVATED表示激活成功 + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` + + > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. 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 a120e9f02..ff1a5e6a9 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 @@ -232,9 +232,26 @@ Import completed. Please start cluster and excute 'show cluster' to verify activ ![](/img/show%20cluster.png) +还可在 CLI 中通过执行 `show activation` 命令查看激活状态，示例如下，状态显示为ACTIVATED表示激活成功 + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` + > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件）。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + ## 常见问题 1. 部署过程中多次提示激活失败 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 b151c5efd..1a1ef6771 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 @@ -259,9 +259,28 @@ It costs 0.030s ![](/img/%E4%BC%81%E4%B8%9A%E7%89%88%E6%BF%80%E6%B4%BB.png) + +还可在 CLI 中通过执行 `show activation` 命令查看激活状态，示例如下，状态显示为ACTIVATED表示激活成功 + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` + + > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + ### 一键启停集群 #### 概述 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 52fc27ecb..3852d297a 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 @@ -233,9 +233,26 @@ Import completed. Please start cluster and excute 'show cluster' to verify activ ![](/img/show%20cluster.png) +还可在 CLI 中通过执行 `show activation` 命令查看激活状态，示例如下，状态显示为ACTIVATED表示激活成功 + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` + > 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件）。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请. + ## 常见问题 1. 部署过程中多次提示激活失败 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 e54a08de7..fdc35dcb2 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 @@ -208,10 +208,21 @@ cd sbin ### 3.6 验证激活 -当看到“Result”字段状态显示为success表示激活成功 - -![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) - +可在 CLI 中通过执行 `show activation` 命令查看激活状态，示例如下，状态显示为 ACTIVATED 表示激活成功 + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` ### 3.7 一键启停集群 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 b9ac9293f..b75c83775 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 @@ -167,7 +167,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 2.6 验证激活 -当看到“ClusterActivationStatus”字段状态显示为ACTIVATED表示激活成功 +可在 CLI 中通过执行 `show activation` 命令查看激活状态，当看到“ClusterActivationStatus”字段状态显示为 ACTIVATED 表示激活成功 ![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png) 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 e83b95239..6a636f940 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,10 +208,21 @@ cd sbin ### 3.6 验证激活 -当看到“Result”字段状态显示为success表示激活成功 - -![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png) - +可在 CLI 中通过执行 `show activation` 命令查看激活状态，示例如下，状态显示为 ACTIVATED 表示激活成功 + +```sql +IoTDB> show activation ++---------------+---------+-----------------------------+ +| LicenseInfo| Usage| Limit| ++---------------+---------+-----------------------------+ +| Status|ACTIVATED| -| +| ExpiredTime| -|2026-04-30T00:00:00.000+08:00| +| DataNodeLimit| 1| Unlimited| +| CpuLimit| 16| Unlimited| +| DeviceLimit| 30| Unlimited| +|TimeSeriesLimit| 72| 1,000,000,000| ++---------------+---------+-----------------------------+ +``` ### 3.7 一键启停集群 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 d1bc4bcd5..5b63ef8e6 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 @@ -173,7 +173,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM ### 2.6 验证激活 -当看到“ClusterActivationStatus”字段状态显示为ACTIVATED表示激活成功 +可在 CLI 中通过执行 `show activation` 命令查看激活状态，当看到“ClusterActivationStatus”字段状态显示为 ACTIVATED 表示激活成功 ![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png)