Skip to content

Commit bb1a1b6

Browse files
leto-bleto-b
authored
add show activation in deploement (#857)
* add show activation in deploement * update cluster
1 parent 1404789 commit bb1a1b6

File tree

24 files changed

+263
-31
lines changed

24 files changed

+263
-31
lines changed

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

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -206,9 +206,22 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM
206206
207207
### 3.7 Verify Activation
208208
209-
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated.
209+
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.
210+
211+
```sql
212+
IoTDB> show activation
213+
+---------------+---------+-----------------------------+
214+
| LicenseInfo| Usage| Limit|
215+
+---------------+---------+-----------------------------+
216+
| Status|ACTIVATED| -|
217+
| ExpiredTime| -|2026-04-30T00:00:00.000+08:00|
218+
| DataNodeLimit| 1| Unlimited|
219+
| CpuLimit| 16| Unlimited|
220+
| DeviceLimit| 30| Unlimited|
221+
|TimeSeriesLimit| 72| 1,000,000,000|
222+
+---------------+---------+-----------------------------+
223+
```
210224
211-
![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png)
212225
213226
### 3.8 One-click Cluster Start and Stop
214227

‎src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM
173173
174174
### 2.6 Verify Activation
175175
176-
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated.
176+
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.
177177
178178
![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png)
179179

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

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -209,9 +209,22 @@ cd sbin
209209
210210
### 3.7 Verify Activation
211211
212-
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated.
212+
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.
213+
214+
```sql
215+
IoTDB> show activation
216+
+---------------+---------+-----------------------------+
217+
| LicenseInfo| Usage| Limit|
218+
+---------------+---------+-----------------------------+
219+
| Status|ACTIVATED| -|
220+
| ExpiredTime| -|2026-04-30T00:00:00.000+08:00|
221+
| DataNodeLimit| 1| Unlimited|
222+
| CpuLimit| 16| Unlimited|
223+
| DeviceLimit| 30| Unlimited|
224+
|TimeSeriesLimit| 72| 1,000,000,000|
225+
+---------------+---------+-----------------------------+
226+
```
213227
214-
![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png)
215228
216229
### 3.8 One-click Cluster Start and Stop
217230

‎src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM
173173

174174
### 2.6 Verify Activation
175175

176-
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated.
176+
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.
177177

178178
![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png)
179179

‎src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -266,6 +266,22 @@ When you see the display of `Activated` on the far right, it indicates successfu
266266

267267
![](/img/%E4%BC%81%E4%B8%9A%E7%89%88%E6%BF%80%E6%B4%BB.png)
268268

269+
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.
270+
271+
```sql
272+
IoTDB> show activation
273+
+---------------+---------+-----------------------------+
274+
| LicenseInfo| Usage| Limit|
275+
+---------------+---------+-----------------------------+
276+
| Status|ACTIVATED| -|
277+
| ExpiredTime| -|2026-04-30T00:00:00.000+08:00|
278+
| DataNodeLimit| 1| Unlimited|
279+
| CpuLimit| 16| Unlimited|
280+
| DeviceLimit| 30| Unlimited|
281+
|TimeSeriesLimit| 72| 1,000,000,000|
282+
+---------------+---------+-----------------------------+
283+
```
284+
269285
> 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.
270286

271287

‎src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -232,6 +232,22 @@ When you see the display "Activated" on the far right, it indicates successful a
232232
233233
![](/img/show%20cluster.png)
234234
235+
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.
236+
237+
```sql
238+
IoTDB> show activation
239+
+---------------+---------+-----------------------------+
240+
| LicenseInfo| Usage| Limit|
241+
+---------------+---------+-----------------------------+
242+
| Status|ACTIVATED| -|
243+
| ExpiredTime| -|2026-04-30T00:00:00.000+08:00|
244+
| DataNodeLimit| 1| Unlimited|
245+
| CpuLimit| 16| Unlimited|
246+
| DeviceLimit| 30| Unlimited|
247+
|TimeSeriesLimit| 72| 1,000,000,000|
248+
+---------------+---------+-----------------------------+
249+
```
250+
235251
236252
> 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.
237253

‎src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -266,6 +266,22 @@ When you see the display of `Activated` on the far right, it indicates successfu
266266

267267
![](/img/%E4%BC%81%E4%B8%9A%E7%89%88%E6%BF%80%E6%B4%BB.png)
268268

269+
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.
270+
271+
```sql
272+
IoTDB> show activation
273+
+---------------+---------+-----------------------------+
274+
| LicenseInfo| Usage| Limit|
275+
+---------------+---------+-----------------------------+
276+
| Status|ACTIVATED| -|
277+
| ExpiredTime| -|2026-04-30T00:00:00.000+08:00|
278+
| DataNodeLimit| 1| Unlimited|
279+
| CpuLimit| 16| Unlimited|
280+
| DeviceLimit| 30| Unlimited|
281+
|TimeSeriesLimit| 72| 1,000,000,000|
282+
+---------------+---------+-----------------------------+
283+
```
284+
269285
> 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.
270286

271287

‎src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -232,6 +232,21 @@ When you see the display "Activated" on the far right, it indicates successful a
232232
233233
![](/img/show%20cluster.png)
234234
235+
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.
236+
237+
```sql
238+
IoTDB> show activation
239+
+---------------+---------+-----------------------------+
240+
| LicenseInfo| Usage| Limit|
241+
+---------------+---------+-----------------------------+
242+
| Status|ACTIVATED| -|
243+
| ExpiredTime| -|2026-04-30T00:00:00.000+08:00|
244+
| DataNodeLimit| 1| Unlimited|
245+
| CpuLimit| 16| Unlimited|
246+
| DeviceLimit| 30| Unlimited|
247+
|TimeSeriesLimit| 72| 1,000,000,000|
248+
+---------------+---------+-----------------------------+
249+
```
235250
236251
> 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.
237252

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

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -205,9 +205,22 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM
205205
206206
### 3.7 Verify Activation
207207
208-
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated.
208+
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.
209+
210+
```sql
211+
IoTDB> show activation
212+
+---------------+---------+-----------------------------+
213+
| LicenseInfo| Usage| Limit|
214+
+---------------+---------+-----------------------------+
215+
| Status|ACTIVATED| -|
216+
| ExpiredTime| -|2026-04-30T00:00:00.000+08:00|
217+
| DataNodeLimit| 1| Unlimited|
218+
| CpuLimit| 16| Unlimited|
219+
| DeviceLimit| 30| Unlimited|
220+
|TimeSeriesLimit| 72| 1,000,000,000|
221+
+---------------+---------+-----------------------------+
222+
```
209223
210-
![](/img/%E9%9B%86%E7%BE%A4-%E9%AA%8C%E8%AF%81.png)
211224
212225
### 3.8 One-click Cluster Start and Stop
213226

‎src/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOM
172172
173173
### 2.6 Verify Activation
174174
175-
Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated.
175+
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.
176176
177177
![](/img/%E5%8D%95%E6%9C%BA-%E9%AA%8C%E8%AF%81.png)
178178

0 commit comments

Comments
 (0)