You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is complete and correct,
55
55
56
56
**Preparation:**
57
57
58
-
- Obtain the official SHA512 checksum: Please contact commercial support.
58
+
- Obtain the official SHA512 checksum.
59
59
60
60
**Verification Steps (using Linux as an example):**
61
61
@@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is complete and correct,
77
77
78
78
**Notes:**
79
79
80
-
- If the verification results do not match, please contact commercial support to obtain a new installation package.
80
+
- If the verification results do not match, please obtain a new installation package.
81
81
- If you encounter a "file not found" prompt during verification, check if the file path is correct or if the installation package was downloaded completely.
82
82
83
83
### 2.3 Environment Requirements
@@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You can find the following
116
116
### 3.3 Importing Built-in Weight Files
117
117
118
118
*If the deployment environment has network connectivity and can access HuggingFace, the system will automatically pull the built-in model weight files. This step can be skipped.*
119
-
*For offline environments, contact commercial support to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.*
119
+
*For offline environments, prepare the model weight folder in advance and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.*
120
120
**NOTE:** Pay attention to the directory hierarchy. The parent directory for all built-in model weights should be `builtin`.
121
121
122
122
### 3.4 Starting AINode
@@ -228,7 +228,7 @@ If you need to upgrade the version of the current AINode, you can refer to the f
228
228
229
229
3. Update built-in model weights (optional)
230
230
231
-
* If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact commercial support to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory.
231
+
* If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). Prepare the latest weight package in advance and replace it in the `data/ainode/models/builtin` directory.
232
232
233
233
4. After the upgrade is completed, you can start the AINode service and check the node status. For specific commands, refer to Sections 3.4 and 3.5.
Copy file name to clipboardExpand all lines: src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
-88Lines changed: 0 additions & 88 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,91 +96,3 @@ For more details, refer to the following documents:
96
96
- [Prometheus Configuration for Pulling Metrics from HTTP Interface](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config)
97
97
- [Grafana Installation and Usage Documentation](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
98
98
- [Grafana Querying Data from Prometheus and Plotting Documentation](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
99
-
100
-
## 4. Apache IoTDB Dashboard
101
-
102
-
The `Apache IoTDB Dashboard` is a companion product of IoTDB, supporting unified centralized operation and maintenance management. It allows monitoring multiple clusters through a single monitoring panel. You can contact the business team to obtain the Dashboard's JSON file.
- Pipe event commit queue size, number of unassigned Pipe events
175
-
- Number of unprocessed events in the Source queue, Source event feeding rate, Processor event processing rate
176
-
- Number of untransmitted events for all Pipe Sinks/Sources, transmission event rate of Pipe connectors
177
-
- Retry queue size and pending handler count of Pipe Sinks; total data size before and after compression and compression duration of Pipe Sinks; batch size and batch interval distribution of Pipe Sinks
178
-
- Pipe memory usage and capacity, number of Pipe phantom references, quantity and total size of linked TsFiles, disk bytes read for TsFile transmission via Pipe
0 commit comments