This is an automated email from the ASF dual-hosted git repository.
CritasWang 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 ad52f8fb Remove commercial contact references from docs (#1169)
ad52f8fb is described below
commit ad52f8fb2bacce51392566ce5f2795d70f76d840
Author: leto-bbq <[email protected]>
AuthorDate: Wed Jun 24 16:27:20 2026 +0800
Remove commercial contact references from docs (#1169)
---
src/.vuepress/sidebar/V1.2.x/en.ts | 1 -
src/.vuepress/sidebar/V1.2.x/zh.ts | 1 -
src/.vuepress/sidebar/V1.3.x/en.ts | 8 --
src/.vuepress/sidebar/V1.3.x/zh.ts | 8 --
src/.vuepress/sidebar/V2.0.x/en-Tree.ts | 8 --
src/.vuepress/sidebar/V2.0.x/zh-Tree.ts | 8 --
.../AINode_Deployment_Upgrade_apache.md | 8 +-
.../AINode_Deployment_apache.md | 2 +-
.../Database-Resources_apache.md | 8 +-
.../Table/Tools-System/Monitor-Tool_apache.md | 88 ---------------------
.../AINode_Deployment_Upgrade_apache.md | 8 +-
.../AINode_Deployment_apache.md | 2 +-
.../Cluster-Deployment_apache.md | 5 +-
.../Database-Resources.md | 8 +-
.../Stand-Alone-Deployment_apache.md | 5 +-
.../Tree/Tools-System/Monitor-Tool_apache.md | 92 ----------------------
src/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md | 72 -----------------
.../Cluster-Deployment_apache.md | 3 +-
.../Database-Resources.md | 8 +-
.../Stand-Alone-Deployment_apache.md | 3 +-
.../V1.3.x/Tools-System/Monitor-Tool_apache.md | 76 ------------------
.../Cluster-Deployment_apache.md | 3 +-
.../Database-Resources.md | 8 +-
.../Stand-Alone-Deployment_apache.md | 3 +-
.../dev-1.3/Tools-System/Monitor-Tool_apache.md | 74 -----------------
.../AINode_Deployment_Upgrade_apache.md | 8 +-
.../AINode_Deployment_apache.md | 2 +-
.../Database-Resources_apache.md | 8 +-
.../Tools-System/Monitor-Tool_apache.md | 88 ---------------------
.../AINode_Deployment_Upgrade_apache.md | 8 +-
.../AINode_Deployment_apache.md | 2 +-
.../Cluster-Deployment_apache.md | 5 +-
.../Database-Resources.md | 8 +-
.../Stand-Alone-Deployment_apache.md | 5 +-
.../latest/Tools-System/Monitor-Tool_apache.md | 92 ----------------------
.../AINode_Deployment_Upgrade_apache.md | 8 +-
.../AINode_Deployment_apache.md | 2 +-
.../Cluster-Deployment_apache.md | 2 +-
.../Database-Resources_apache.md | 8 +-
.../Stand-Alone-Deployment_apache.md | 2 +-
.../Table/Tools-System/Monitor-Tool_apache.md | 84 --------------------
.../AINode_Deployment_Upgrade_apache.md | 8 +-
.../AINode_Deployment_apache.md | 2 +-
.../Cluster-Deployment_apache.md | 2 +-
.../Database-Resources_apache.md | 8 +-
.../Stand-Alone-Deployment_apache.md | 2 +-
.../Tree/Tools-System/Monitor-Tool_apache.md | 84 --------------------
.../UserGuide/V1.2.x/Tools-System/Monitor-Tool.md | 67 ----------------
.../Cluster-Deployment_apache.md | 2 +-
.../Stand-Alone-Deployment_apache.md | 2 +-
.../V1.3.x/Tools-System/Monitor-Tool_apache.md | 69 ----------------
.../Cluster-Deployment_apache.md | 4 +-
.../Stand-Alone-Deployment_apache.md | 4 +-
.../dev-1.3/Tools-System/Monitor-Tool_apache.md | 67 ----------------
.../AINode_Deployment_Upgrade_apache.md | 8 +-
.../AINode_Deployment_apache.md | 2 +-
.../Cluster-Deployment_apache.md | 2 +-
.../Database-Resources_apache.md | 8 +-
.../Stand-Alone-Deployment_apache.md | 2 +-
.../Tools-System/Monitor-Tool_apache.md | 84 --------------------
.../AINode_Deployment_Upgrade_apache.md | 8 +-
.../AINode_Deployment_apache.md | 2 +-
.../Cluster-Deployment_apache.md | 2 +-
.../Database-Resources_apache.md | 8 +-
.../Stand-Alone-Deployment_apache.md | 2 +-
.../latest/Tools-System/Monitor-Tool_apache.md | 84 --------------------
66 files changed, 106 insertions(+), 1269 deletions(-)
diff --git a/src/.vuepress/sidebar/V1.2.x/en.ts
b/src/.vuepress/sidebar/V1.2.x/en.ts
index 8b97abb3..5c418cee 100644
--- a/src/.vuepress/sidebar/V1.2.x/en.ts
+++ b/src/.vuepress/sidebar/V1.2.x/en.ts
@@ -178,7 +178,6 @@ export const enSidebar = {
prefix: 'Reference/',
// children: 'structure',
children: [
- { text: 'UDF Libraries', link: 'UDF-Libraries' },
{ text: 'Common Config Manual', link: 'Common-Config-Manual' },
{ text: 'Status Codes', link: 'Status-Codes' },
{ text: 'Keywords', link: 'Keywords' },
diff --git a/src/.vuepress/sidebar/V1.2.x/zh.ts
b/src/.vuepress/sidebar/V1.2.x/zh.ts
index c5ec4145..37f76cac 100644
--- a/src/.vuepress/sidebar/V1.2.x/zh.ts
+++ b/src/.vuepress/sidebar/V1.2.x/zh.ts
@@ -163,7 +163,6 @@ export const zhSidebar = {
prefix: 'Reference/',
// children: 'structure',
children: [
- { text: 'UDF函数库', link: 'UDF-Libraries' },
{ text: '配置参数', link: 'Common-Config-Manual' },
{ text: 'ConfigNode配置参数', link: 'ConfigNode-Config-Manual' },
{ text: 'DataNode配置参数', link: 'DataNode-Config-Manual' },
diff --git a/src/.vuepress/sidebar/V1.3.x/en.ts
b/src/.vuepress/sidebar/V1.3.x/en.ts
index 820d9172..90cd8a2e 100644
--- a/src/.vuepress/sidebar/V1.3.x/en.ts
+++ b/src/.vuepress/sidebar/V1.3.x/en.ts
@@ -255,7 +255,6 @@ export const enSidebar = {
{ text: 'Apache Zeppelin', link: 'Zeppelin-IoTDB' },
{ text: 'Grafana', link: 'Grafana-Connector' },
{ text: 'Grafana Plugin', link: 'Grafana-Plugin' },
- { text: 'DataEase', link: 'DataEase' },
],
},
{
@@ -265,13 +264,6 @@ export const enSidebar = {
{ text: 'DBeaver', link: 'DBeaver' },
],
},
- {
- text: 'IoT Platform',
- collapsible: true,
- children: [
- { text: 'ThingsBoard', link: 'Thingsboard' },
- ],
- },
],
},
{
diff --git a/src/.vuepress/sidebar/V1.3.x/zh.ts
b/src/.vuepress/sidebar/V1.3.x/zh.ts
index 6556cd21..9782b988 100644
--- a/src/.vuepress/sidebar/V1.3.x/zh.ts
+++ b/src/.vuepress/sidebar/V1.3.x/zh.ts
@@ -246,7 +246,6 @@ export const zhSidebar = {
{ text: 'Apache Zeppelin', link: 'Zeppelin-IoTDB_apache' },
{ text: 'Grafana', link: 'Grafana-Connector' },
{ text: 'Grafana插件', link: 'Grafana-Plugin' },
- { text: 'DataEase', link: 'DataEase' },
],
},
{
@@ -256,13 +255,6 @@ export const zhSidebar = {
{ text: 'DBeaver', link: 'DBeaver' },
],
},
- {
- text: '物联网平台',
- collapsible: true,
- children: [
- { text: 'ThingsBoard', link: 'Thingsboard' },
- ],
- },
],
},
{
diff --git a/src/.vuepress/sidebar/V2.0.x/en-Tree.ts
b/src/.vuepress/sidebar/V2.0.x/en-Tree.ts
index faff59d9..8d692b69 100644
--- a/src/.vuepress/sidebar/V2.0.x/en-Tree.ts
+++ b/src/.vuepress/sidebar/V2.0.x/en-Tree.ts
@@ -249,7 +249,6 @@ export const enSidebar = {
{ text: 'Apache Zeppelin', link: 'Zeppelin-IoTDB' },
{ text: 'Grafana', link: 'Grafana-Connector' },
{ text: 'Grafana Plugin', link: 'Grafana-Plugin' },
- { text: 'DataEase', link: 'DataEase' },
],
},
{
@@ -259,13 +258,6 @@ export const enSidebar = {
{ text: 'DBeaver', link: 'DBeaver' },
],
},
- {
- text: 'IoT Platform',
- collapsible: true,
- children: [
- { text: 'ThingsBoard', link: 'Thingsboard' },
- ],
- },
],
},
{
diff --git a/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts
b/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts
index 1318cee3..3d39fadf 100644
--- a/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts
+++ b/src/.vuepress/sidebar/V2.0.x/zh-Tree.ts
@@ -240,7 +240,6 @@ export const zhSidebar = {
{ text: 'Apache Zeppelin', link: 'Zeppelin-IoTDB_apache' },
{ text: 'Grafana', link: 'Grafana-Connector' },
{ text: 'Grafana插件', link: 'Grafana-Plugin' },
- { text: 'DataEase', link: 'DataEase' },
],
},
{
@@ -250,13 +249,6 @@ export const zhSidebar = {
{ text: 'DBeaver', link: 'DBeaver' },
],
},
- {
- text: '物联网平台',
- collapsible: true,
- children: [
- { text: 'ThingsBoard', link: 'Thingsboard' },
- ],
- },
],
},
{
diff --git
a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
index 727d2736..646a9d42 100644
---
a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+++
b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is
complete and correct,
**Preparation:**
-- Obtain the official SHA512 checksum: Please contact commercial support.
+- Obtain the official SHA512 checksum.
**Verification Steps (using Linux as an example):**
@@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is
complete and correct,
**Notes:**
-- If the verification results do not match, please contact commercial support
to obtain a new installation package.
+- If the verification results do not match, please obtain a new installation
package.
- 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.
### 2.3 Environment Requirements
@@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You
can find the following
### 3.3 Importing Built-in Weight Files
*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.*
-*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.*
+*For offline environments, prepare the model weight folder in advance and
place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.*
**NOTE:** Pay attention to the directory hierarchy. The parent directory for
all built-in model weights should be `builtin`.
### 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
3. Update built-in model weights (optional)
- * 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.
+ * 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.
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.
diff --git
a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
index 785acb2d..4b1fc637 100644
---
a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
+++
b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You
can find the following
> Offline environment only (Online environments can skip this step)
>
-Contact commercial support to obtain the model weight files, then place them
in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
+Prepare the model weight files in advance, then place them in the
/IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
### 3.4 Start AINode
diff --git
a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
index 998d4e6b..6109d99b 100644
---
a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
+++
b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
@@ -72,11 +72,11 @@
<td>48core</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
@@ -136,11 +136,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
diff --git a/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
b/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
index 6ca1d6a0..406cdbb3 100644
--- a/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
+++ b/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
@@ -96,91 +96,3 @@ For more details, refer to the following documents:
- [Prometheus Configuration for Pulling Metrics from HTTP
Interface](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config)
- [Grafana Installation and Usage
Documentation](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
- [Grafana Querying Data from Prometheus and Plotting
Documentation](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## 4. Apache IoTDB Dashboard
-
-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.
-
-
-
-
-
-### 4.1 Cluster Overview
-
-You can monitor, but not limited to:
-
-- Total CPU cores, total memory space, total disk space of the cluster.
-- Number of ConfigNodes and DataNodes in the cluster.
-- Cluster uptime.
-- Cluster write speed.
-- Current CPU, memory, and disk usage of each node in the cluster.
-- Node-specific information.
-
-
-
-### 4.2 Data Writing
-
-You can monitor, but not limited to:
-
-- Average write latency, median latency, 99th percentile latency.
-- Number and size of WAL files.
-- Node WAL flush SyncBuffer latency.
-
-
-
-### 4.3 Data Query
-
-You can monitor, but not limited to:
-
-- Node query loading time series metadata latency.
-- Node query reading time series latency.
-- Node query modifying time series metadata latency.
-- Node query loading Chunk metadata list latency.
-- Node query modifying Chunk metadata latency.
-- Node query filtering by Chunk metadata latency.
-- Node query constructing Chunk Reader latency average.
-
-
-
-### 4.4 Storage Engine
-
-You can monitor, but not limited to:
-
-- Number and size of files by type.
-- Number and size of TsFiles in various stages.
-- Number and latency of various tasks.
-
-
-
-### 4.5 System Monitoring
-
-You can monitor, but not limited to:
-
-- System memory, swap memory, process memory.
-- Disk space, file count, file size.
-- JVM GC time ratio, GC count by type, GC data volume, heap memory usage by
generation.
-- Network transmission rate, packet sending rate.
-
-
-
-
-
-
-
-### 4.6 Data Synchronization
-
-Including but not limited to:
-
-- Pipe event commit queue size, number of unassigned Pipe events
-- Number of unprocessed events in the Source queue, Source event feeding rate,
Processor event processing rate
-- Number of untransmitted events for all Pipe Sinks/Sources, transmission
event rate of Pipe connectors
-- 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
-- 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
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
index 6d27f895..6dc8dd93 100644
---
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+++
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is
complete and correct,
**Preparation:**
-- Obtain the official SHA512 checksum: Please contact commercial support.
+- Obtain the official SHA512 checksum.
**Verification Steps (using Linux as an example):**
@@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is
complete and correct,
**Notes:**
-- If the verification results do not match, please contact commercial support
to obtain a new installation package.
+- If the verification results do not match, please obtain a new installation
package.
- 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.
### 2.3 Environment Requirements
@@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You
can find the following
### 3.3 Importing Built-in Weight Files
*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.*
-*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.*
+*For offline environments, prepare the model weight folder in advance and
place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.*
**NOTE:** Pay attention to the directory hierarchy. The parent directory for
all built-in model weights should be `builtin`.
### 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
3. Update built-in model weights (optional)
- * 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.
+ * 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.
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.
diff --git
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md
index e9fdac33..3a462bf6 100644
---
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md
+++
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You
can find the following
> Offline environment only (Online environments can skip this step)
>
- Contact commercial support to obtain the model weight files, then place them
in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
+ Prepare the model weight files in advance, then place them in the
/IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
### 3.4 Start AINode
diff --git
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index d5e583b1..b0c03395 100644
---
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -229,7 +229,7 @@ You can use the `show cluster` command to view cluster
information:
-> 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 [...]
+> 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 [...]
### 3.6 One-click Cluster Start and Stop
@@ -500,8 +500,7 @@ For more details on cluster maintenance, please refer to:
[Cluster Maintenance](
Step 1: Please check the startup log to see if any parameters that cannot
be changed after the first startup have been modified.
- Step 2: Please check the startup log for any other abnormalities. If there
are any abnormal phenomena in the log, please contact commercial support for
consultation on solutions.
-
+ Step 2: Please check the startup log for any other abnormalities.
Step 3: If it is the first deployment or data can be deleted, you can also
clean up the environment according to the following steps, redeploy, and
restart.
Step 4: Clean up the environment:
diff --git
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources.md
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources.md
index 3a0a5b74..d12dd5d9 100644
--- a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources.md
+++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources.md
@@ -72,11 +72,11 @@
<td>48core</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
@@ -137,11 +137,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
diff --git
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index c2f10d02..cbd6ebdb 100644
---
a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -197,7 +197,7 @@ When the status is all running, it indicates that the
service has started succes
-> 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 commerci [...]
+> 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 reapply.
## 3. Common Questions
@@ -205,8 +205,7 @@ When the status is all running, it indicates that the
service has started succes
Step 1: Please check the startup log to see if any parameters that cannot
be changed after the first startup have been modified.
- Step 2: Please check the startup log for any other abnormalities. If there
are any abnormal phenomena in the log, please contact commercial support for
consultation on solutions.
-
+ Step 2: Please check the startup log for any other abnormalities.
Step 3: If it is the first deployment or data can be deleted, you can also
clean up the environment according to the following steps, redeploy, and
restart.
Step 4: Clean up the environment:
diff --git a/src/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md
b/src/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md
index d4ed0675..b7107644 100644
--- a/src/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md
+++ b/src/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md
@@ -106,95 +106,3 @@ The following documents may help you have a good journey
with Prometheus and Gra
[Grafana
getting_started](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana query metrics from
Prometheus](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## 2. Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard` is available as a supplement to IoTDB, designed for
unified centralized operations and management. With it, multiple clusters can
be monitored through a single panel. You can access the Dashboard's Json file
by contacting Commerce.
-
-
-
-
-
-
-
-
-### 2.1 Cluster Overview
-
-Including but not limited to:
-
-- Total cluster CPU cores, memory space, and hard disk space.
-- Number of ConfigNodes and DataNodes in the cluster.
-- Cluster uptime duration.
-- Cluster write speed.
-- Current CPU, memory, and disk usage across all nodes in the cluster.
-- Information on individual nodes.
-
-
-
-
-### 2.2 Data Writing
-
-Including but not limited to:
-
-- Average write latency, median latency, and the 99% percentile latency.
-- Number and size of WAL files.
-- Node WAL flush SyncBuffer latency.
-
-
-
-### 2.3 Data Querying
-
-Including but not limited to:
-
-- Node query load times for time series metadata.
-- Node read duration for time series.
-- Node edit duration for time series metadata.
-- Node query load time for Chunk metadata list.
-- Node edit duration for Chunk metadata.
-- Node filtering duration based on Chunk metadata.
-- Average time to construct a Chunk Reader.
-
-
-
-### 2.4 Storage Engine
-
-Including but not limited to:
-
-- File count and sizes by type.
-- The count and size of TsFiles at various stages.
-- Number and duration of various tasks.
-
-
-
-### 2.5 System Monitoring
-
-Including but not limited to:
-
-- System memory, swap memory, and process memory.
-- Disk space, file count, and file sizes.
-- JVM GC time percentage, GC occurrences by type, GC volume, and heap memory
usage across generations.
-- Network transmission rate, packet sending rate
-
-
-
-
-
-
-
-### 2.6 Data Synchronization
-
-Including but not limited to:
-
-- Pipe event commit queue size, number of unassigned Pipe events
-- Number of unprocessed events in the Source queue, Source event feeding rate,
Processor event processing rate
-- Number of untransmitted events for all Pipe Sinks/Sources, transmission
event rate of Pipe connectors
-- 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
-- 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
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/src/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md
b/src/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md
index feef5f5c..58ea47e1 100644
--- a/src/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md
+++ b/src/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md
@@ -104,75 +104,3 @@ The following documents may help you have a good journey
with Prometheus and Gra
[Grafana
getting_started](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana query metrics from
Prometheus](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard` is available as a supplement to IoTDB Enterprise
Edition, designed for unified centralized operations and management. With it,
multiple clusters can be monitored through a single panel. You can access the
Dashboard's Json file by contacting Commerce.
-
-
-
-
-
-
-### Cluster Overview
-
-Including but not limited to:
-
-- Total cluster CPU cores, memory space, and hard disk space.
-- Number of ConfigNodes and DataNodes in the cluster.
-- Cluster uptime duration.
-- Cluster write speed.
-- Current CPU, memory, and disk usage across all nodes in the cluster.
-- Information on individual nodes.
-
-
-
-
-### Data Writing
-
-Including but not limited to:
-
-- Average write latency, median latency, and the 99% percentile latency.
-- Number and size of WAL files.
-- Node WAL flush SyncBuffer latency.
-
-
-
-### Data Querying
-
-Including but not limited to:
-
-- Node query load times for time series metadata.
-- Node read duration for time series.
-- Node edit duration for time series metadata.
-- Node query load time for Chunk metadata list.
-- Node edit duration for Chunk metadata.
-- Node filtering duration based on Chunk metadata.
-- Average time to construct a Chunk Reader.
-
-
-
-### Storage Engine
-
-Including but not limited to:
-
-- File count and sizes by type.
-- The count and size of TsFiles at various stages.
-- Number and duration of various tasks.
-
-
-
-### System Monitoring
-
-Including but not limited to:
-
-- System memory, swap memory, and process memory.
-- Disk space, file count, and file sizes.
-- JVM GC time percentage, GC occurrences by type, GC volume, and heap memory
usage across generations.
-- Network transmission rate, packet sending rate
-
-
-
-
-
-
\ No newline at end of file
diff --git
a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index 6f2e00c3..30cb5362 100644
---
a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -415,8 +415,7 @@ sbin/remove-datanode.bat [datanode_id]
Step 1: Please check the startup log to see if any parameters that cannot
be changed after the first startup have been modified.
- Step 2: Please check the startup log for any other abnormalities. If there
are any abnormal phenomena in the log, please contact commercial support for
consultation on solutions.
-
+ Step 2: Please check the startup log for any other abnormalities.
Step 3: If it is the first deployment or data can be deleted, you can also
clean up the environment according to the following steps, redeploy, and
restart.
Step 4: Clean up the environment:
diff --git
a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md
b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md
index b94af193..500b0d63 100644
--- a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md
+++ b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Database-Resources.md
@@ -72,11 +72,11 @@
<td>48core</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
@@ -134,11 +134,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
diff --git
a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index 51d54fe1..119874e5 100644
---
a/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -179,8 +179,7 @@ When the status is all running, it indicates that the
service has started succes
Step 1: Please check the startup log to see if any parameters that cannot
be changed after the first startup have been modified.
- Step 2: Please check the startup log for any other abnormalities. If there
are any abnormal phenomena in the log, please contact commercial support for
consultation on solutions.
-
+ Step 2: Please check the startup log for any other abnormalities.
Step 3: If it is the first deployment or data can be deleted, you can also
clean up the environment according to the following steps, redeploy, and
restart.
Step 4: Clean up the environment:
diff --git a/src/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md
b/src/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md
index aa38f195..375db1e7 100644
--- a/src/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md
+++ b/src/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md
@@ -21,8 +21,6 @@
# Monitor Tool
-The deployment of monitoring tools can refer to the document [Monitoring Panel
Deployment](../Deployment-and-Maintenance/Monitoring-panel-deployment.md)
section.
-
## Prometheus
### The mapping from metric type to prometheus format
@@ -106,77 +104,3 @@ The following documents may help you have a good journey
with Prometheus and Gra
[Grafana
getting_started](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana query metrics from
Prometheus](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard` is available as a supplement to IoTDB, designed for
unified centralized operations and management. With it, multiple clusters can
be monitored through a single panel. You can access the Dashboard's Json file
by contacting Commerce.
-
-
-
-
-
-
-
-
-### Cluster Overview
-
-Including but not limited to:
-
-- Total cluster CPU cores, memory space, and hard disk space.
-- Number of ConfigNodes and DataNodes in the cluster.
-- Cluster uptime duration.
-- Cluster write speed.
-- Current CPU, memory, and disk usage across all nodes in the cluster.
-- Information on individual nodes.
-
-
-
-
-### Data Writing
-
-Including but not limited to:
-
-- Average write latency, median latency, and the 99% percentile latency.
-- Number and size of WAL files.
-- Node WAL flush SyncBuffer latency.
-
-
-
-### Data Querying
-
-Including but not limited to:
-
-- Node query load times for time series metadata.
-- Node read duration for time series.
-- Node edit duration for time series metadata.
-- Node query load time for Chunk metadata list.
-- Node edit duration for Chunk metadata.
-- Node filtering duration based on Chunk metadata.
-- Average time to construct a Chunk Reader.
-
-
-
-### Storage Engine
-
-Including but not limited to:
-
-- File count and sizes by type.
-- The count and size of TsFiles at various stages.
-- Number and duration of various tasks.
-
-
-
-### System Monitoring
-
-Including but not limited to:
-
-- System memory, swap memory, and process memory.
-- Disk space, file count, and file sizes.
-- JVM GC time percentage, GC occurrences by type, GC volume, and heap memory
usage across generations.
-- Network transmission rate, packet sending rate
-
-
-
-
-
-
diff --git
a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index 23590ad6..79ed8af0 100644
---
a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -409,8 +409,7 @@ remove datanode [datanode_id]
Step 1: Please check the startup log to see if any parameters that cannot
be changed after the first startup have been modified.
- Step 2: Please check the startup log for any other abnormalities. If there
are any abnormal phenomena in the log, please contact commercial support for
consultation on solutions.
-
+ Step 2: Please check the startup log for any other abnormalities.
Step 3: If it is the first deployment or data can be deleted, you can also
clean up the environment according to the following steps, redeploy, and
restart.
Step 4: Clean up the environment:
diff --git
a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md
b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md
index b94af193..500b0d63 100644
--- a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md
+++ b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Database-Resources.md
@@ -72,11 +72,11 @@
<td>48core</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
@@ -134,11 +134,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
diff --git
a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index 527875f3..58e00524 100644
---
a/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -183,8 +183,7 @@ When the status is all running, it indicates that the
service has started succes
Step 1: Please check the startup log to see if any parameters that cannot
be changed after the first startup have been modified.
- Step 2: Please check the startup log for any other abnormalities. If there
are any abnormal phenomena in the log, please contact commercial support for
consultation on solutions.
-
+ Step 2: Please check the startup log for any other abnormalities.
Step 3: If it is the first deployment or data can be deleted, you can also
clean up the environment according to the following steps, redeploy, and
restart.
Step 4: Clean up the environment:
diff --git a/src/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md
b/src/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md
index aa38f195..820bf5e6 100644
--- a/src/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md
+++ b/src/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md
@@ -106,77 +106,3 @@ The following documents may help you have a good journey
with Prometheus and Gra
[Grafana
getting_started](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana query metrics from
Prometheus](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard` is available as a supplement to IoTDB, designed for
unified centralized operations and management. With it, multiple clusters can
be monitored through a single panel. You can access the Dashboard's Json file
by contacting Commerce.
-
-
-
-
-
-
-
-
-### Cluster Overview
-
-Including but not limited to:
-
-- Total cluster CPU cores, memory space, and hard disk space.
-- Number of ConfigNodes and DataNodes in the cluster.
-- Cluster uptime duration.
-- Cluster write speed.
-- Current CPU, memory, and disk usage across all nodes in the cluster.
-- Information on individual nodes.
-
-
-
-
-### Data Writing
-
-Including but not limited to:
-
-- Average write latency, median latency, and the 99% percentile latency.
-- Number and size of WAL files.
-- Node WAL flush SyncBuffer latency.
-
-
-
-### Data Querying
-
-Including but not limited to:
-
-- Node query load times for time series metadata.
-- Node read duration for time series.
-- Node edit duration for time series metadata.
-- Node query load time for Chunk metadata list.
-- Node edit duration for Chunk metadata.
-- Node filtering duration based on Chunk metadata.
-- Average time to construct a Chunk Reader.
-
-
-
-### Storage Engine
-
-Including but not limited to:
-
-- File count and sizes by type.
-- The count and size of TsFiles at various stages.
-- Number and duration of various tasks.
-
-
-
-### System Monitoring
-
-Including but not limited to:
-
-- System memory, swap memory, and process memory.
-- Disk space, file count, and file sizes.
-- JVM GC time percentage, GC occurrences by type, GC volume, and heap memory
usage across generations.
-- Network transmission rate, packet sending rate
-
-
-
-
-
-
diff --git
a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
index ff02d4c3..687e17f0 100644
---
a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+++
b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is
complete and correct,
**Preparation:**
-- Obtain the official SHA512 checksum: Please contact commercial support.
+- Obtain the official SHA512 checksum.
**Verification Steps (using Linux as an example):**
@@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is
complete and correct,
**Notes:**
-- If the verification results do not match, please contact commercial support
to obtain a new installation package.
+- If the verification results do not match, please obtain a new installation
package.
- 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.
### 2.3 Environment Requirements
@@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You
can find the following
### 3.3 Importing Built-in Weight Files
*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.*
-*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.*
+*For offline environments, prepare the model weight folder in advance and
place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.*
**NOTE:** Pay attention to the directory hierarchy. The parent directory for
all built-in model weights should be `builtin`.
### 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
3. Update built-in model weights (optional)
- * 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.
+ * 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.
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.
diff --git
a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
index 785acb2d..4b1fc637 100644
---
a/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
+++
b/src/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You
can find the following
> Offline environment only (Online environments can skip this step)
>
-Contact commercial support to obtain the model weight files, then place them
in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
+Prepare the model weight files in advance, then place them in the
/IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
### 3.4 Start AINode
diff --git
a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md
b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md
index 998d4e6b..6109d99b 100644
---
a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md
+++
b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md
@@ -72,11 +72,11 @@
<td>48core</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
@@ -136,11 +136,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
diff --git a/src/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md
b/src/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md
index 71126139..db25ef20 100644
--- a/src/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md
+++ b/src/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md
@@ -95,91 +95,3 @@ For more details, refer to the following documents:
- [Prometheus Configuration for Pulling Metrics from HTTP
Interface](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config)
- [Grafana Installation and Usage
Documentation](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
- [Grafana Querying Data from Prometheus and Plotting
Documentation](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## 4. Apache IoTDB Dashboard
-
-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.
-
-
-
-
-
-### 4.1 Cluster Overview
-
-You can monitor, but not limited to:
-
-- Total CPU cores, total memory space, total disk space of the cluster.
-- Number of ConfigNodes and DataNodes in the cluster.
-- Cluster uptime.
-- Cluster write speed.
-- Current CPU, memory, and disk usage of each node in the cluster.
-- Node-specific information.
-
-
-
-### 4.2 Data Writing
-
-You can monitor, but not limited to:
-
-- Average write latency, median latency, 99th percentile latency.
-- Number and size of WAL files.
-- Node WAL flush SyncBuffer latency.
-
-
-
-### 4.3 Data Query
-
-You can monitor, but not limited to:
-
-- Node query loading time series metadata latency.
-- Node query reading time series latency.
-- Node query modifying time series metadata latency.
-- Node query loading Chunk metadata list latency.
-- Node query modifying Chunk metadata latency.
-- Node query filtering by Chunk metadata latency.
-- Node query constructing Chunk Reader latency average.
-
-
-
-### 4.4 Storage Engine
-
-You can monitor, but not limited to:
-
-- Number and size of files by type.
-- Number and size of TsFiles in various stages.
-- Number and latency of various tasks.
-
-
-
-### 4.5 System Monitoring
-
-You can monitor, but not limited to:
-
-- System memory, swap memory, process memory.
-- Disk space, file count, file size.
-- JVM GC time ratio, GC count by type, GC data volume, heap memory usage by
generation.
-- Network transmission rate, packet sending rate.
-
-
-
-
-
-
-
-### 4.6 Data Synchronization
-
-Including but not limited to:
-
-- Pipe event commit queue size, number of unassigned Pipe events
-- Number of unprocessed events in the Source queue, Source event feeding rate,
Processor event processing rate
-- Number of untransmitted events for all Pipe Sinks/Sources, transmission
event rate of Pipe connectors
-- 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
-- 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
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
index 5041947c..99edbc3d 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is
complete and correct,
**Preparation:**
-- Obtain the official SHA512 checksum: Please contact commercial support.
+- Obtain the official SHA512 checksum.
**Verification Steps (using Linux as an example):**
@@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is
complete and correct,
**Notes:**
-- If the verification results do not match, please contact commercial support
to obtain a new installation package.
+- If the verification results do not match, please obtain a new installation
package.
- 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.
### 2.3 Environment Requirements
@@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You
can find the following
### 3.3 Importing Built-in Weight Files
*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.*
-*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.*
+*For offline environments, prepare the model weight folder in advance and
place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.*
**NOTE:** Pay attention to the directory hierarchy. The parent directory for
all built-in model weights should be `builtin`.
### 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
3. Update built-in model weights (optional)
- * 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.
+ * 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.
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.
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md
b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md
index e9fdac33..3a462bf6 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You
can find the following
> Offline environment only (Online environments can skip this step)
>
- Contact commercial support to obtain the model weight files, then place them
in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
+ Prepare the model weight files in advance, then place them in the
/IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
### 3.4 Start AINode
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index d5e583b1..b0c03395 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -229,7 +229,7 @@ You can use the `show cluster` command to view cluster
information:
-> 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 [...]
+> 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 [...]
### 3.6 One-click Cluster Start and Stop
@@ -500,8 +500,7 @@ For more details on cluster maintenance, please refer to:
[Cluster Maintenance](
Step 1: Please check the startup log to see if any parameters that cannot
be changed after the first startup have been modified.
- Step 2: Please check the startup log for any other abnormalities. If there
are any abnormal phenomena in the log, please contact commercial support for
consultation on solutions.
-
+ Step 2: Please check the startup log for any other abnormalities.
Step 3: If it is the first deployment or data can be deleted, you can also
clean up the environment according to the following steps, redeploy, and
restart.
Step 4: Clean up the environment:
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.md
b/src/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.md
index 4f6ebf7d..13b225a3 100644
--- a/src/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.md
+++ b/src/UserGuide/latest/Deployment-and-Maintenance/Database-Resources.md
@@ -72,11 +72,11 @@
<td>48core</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
@@ -136,11 +136,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>Please contact commercial support for consultation</td>
+ <td>Evaluate as needed</td>
</tr>
<tr>
<td>Over 10000000</td>
- <td colspan="4">Please contact commercial support for
consultation</td>
+ <td colspan="4">Evaluate as needed</td>
</tr>
</tbody>
</table>
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index c2f10d02..cbd6ebdb 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -197,7 +197,7 @@ When the status is all running, it indicates that the
service has started succes
-> 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 commerci [...]
+> 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 reapply.
## 3. Common Questions
@@ -205,8 +205,7 @@ When the status is all running, it indicates that the
service has started succes
Step 1: Please check the startup log to see if any parameters that cannot
be changed after the first startup have been modified.
- Step 2: Please check the startup log for any other abnormalities. If there
are any abnormal phenomena in the log, please contact commercial support for
consultation on solutions.
-
+ Step 2: Please check the startup log for any other abnormalities.
Step 3: If it is the first deployment or data can be deleted, you can also
clean up the environment according to the following steps, redeploy, and
restart.
Step 4: Clean up the environment:
diff --git a/src/UserGuide/latest/Tools-System/Monitor-Tool_apache.md
b/src/UserGuide/latest/Tools-System/Monitor-Tool_apache.md
index d4ed0675..b7107644 100644
--- a/src/UserGuide/latest/Tools-System/Monitor-Tool_apache.md
+++ b/src/UserGuide/latest/Tools-System/Monitor-Tool_apache.md
@@ -106,95 +106,3 @@ The following documents may help you have a good journey
with Prometheus and Gra
[Grafana
getting_started](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana query metrics from
Prometheus](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## 2. Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard` is available as a supplement to IoTDB, designed for
unified centralized operations and management. With it, multiple clusters can
be monitored through a single panel. You can access the Dashboard's Json file
by contacting Commerce.
-
-
-
-
-
-
-
-
-### 2.1 Cluster Overview
-
-Including but not limited to:
-
-- Total cluster CPU cores, memory space, and hard disk space.
-- Number of ConfigNodes and DataNodes in the cluster.
-- Cluster uptime duration.
-- Cluster write speed.
-- Current CPU, memory, and disk usage across all nodes in the cluster.
-- Information on individual nodes.
-
-
-
-
-### 2.2 Data Writing
-
-Including but not limited to:
-
-- Average write latency, median latency, and the 99% percentile latency.
-- Number and size of WAL files.
-- Node WAL flush SyncBuffer latency.
-
-
-
-### 2.3 Data Querying
-
-Including but not limited to:
-
-- Node query load times for time series metadata.
-- Node read duration for time series.
-- Node edit duration for time series metadata.
-- Node query load time for Chunk metadata list.
-- Node edit duration for Chunk metadata.
-- Node filtering duration based on Chunk metadata.
-- Average time to construct a Chunk Reader.
-
-
-
-### 2.4 Storage Engine
-
-Including but not limited to:
-
-- File count and sizes by type.
-- The count and size of TsFiles at various stages.
-- Number and duration of various tasks.
-
-
-
-### 2.5 System Monitoring
-
-Including but not limited to:
-
-- System memory, swap memory, and process memory.
-- Disk space, file count, and file sizes.
-- JVM GC time percentage, GC occurrences by type, GC volume, and heap memory
usage across generations.
-- Network transmission rate, packet sending rate
-
-
-
-
-
-
-
-### 2.6 Data Synchronization
-
-Including but not limited to:
-
-- Pipe event commit queue size, number of unassigned Pipe events
-- Number of unprocessed events in the Source queue, Source event feeding rate,
Processor event processing rate
-- Number of untransmitted events for all Pipe Sinks/Sources, transmission
event rate of Pipe connectors
-- 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
-- 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
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
index b09ef486..e67d1ded 100644
---
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+++
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ AINode 安装包（`apache-iotdb-<version>-ainode-bin.zip`）解压后关键目
**准备工作：**
-* 获取官方发布的 SHA512 校验码：请联系商业支持获取
+* 获取官方发布的 SHA512 校验码
**校验步骤（以 linux 为例）：**
@@ -79,7 +79,7 @@
b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4
**注意事项：**
-* 若校验结果不一致，请联系商业支持重新获取安装包
+* 若校验结果不一致，请重新获取安装包
* 校验过程中若出现"文件不存在"提示，需检查文件路径是否正确或安装包是否完整下载
### 2.3 环境要求
@@ -119,7 +119,7 @@ AINode 支持修改一些必要的参数。可以在 `/IOTDB_AINODE_HOME/conf/io
若部署环境可联网且能连通 HuggingFace 环境，系统会自动拉取内置模型权重文件，可忽略本步骤。
-若为离线环境，联系商业支持获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。
+若为离线环境，需提前准备模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。
**NOTE：**注意目录层级，最终所有内置模型权重的父目录都是 `builtin `。
@@ -231,7 +231,7 @@ IoTDB> show cluster
* 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置
3. 更新内置模型权重（可选）
- *
若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至
`data/ainode/models/builtin` 目录
+ *
若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。需提前准备最新权重包，并将权重包替换至
`data/ainode/models/builtin` 目录
4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。
diff --git
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
index 5badae7a..211e499d 100644
---
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
+++
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -127,7 +127,7 @@ AINode 支持修改一些必要的参数。可以在 `conf/iotdb-ainode.properti
> 仅离线环境，在线环境可忽略本步骤
>
-联系商业支持获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。
+需提前准备模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。
### 3.4 启动 AINode
diff --git
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index b0240d2c..c6e75bb8 100644
---
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -438,7 +438,7 @@ remove datanode [datanode_id]
1. Confignode节点启动失败
- 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ - 步骤 2: 请查看启动日志，检查是否出现其他异常。
- 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
- 清理环境：
diff --git
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
index c1b64662..18a0703d 100644
---
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
+++
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
@@ -73,11 +73,11 @@
<td>48核</td>
<td>1</td>
<td>2</td>
- <td>请联系商业支持咨询</td>
+ <td>建议按需评估</td>
</tr>
<tr>
<td>1000w以上</td>
- <td colspan="4">请联系商业支持咨询</td>
+ <td colspan="4">建议按需评估</td>
</tr>
</tbody>
</table>
@@ -137,11 +137,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>请联系商业支持咨询</td>
+ <td>建议按需评估</td>
</tr>
<tr>
<td>1000w以上</td>
- <td colspan="4">请联系商业支持咨询</td>
+ <td colspan="4">建议按需评估</td>
</tr>
</tbody>
</table>
diff --git
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index e2f6a5b5..c5265c72 100644
---
a/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/zh/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -183,7 +183,7 @@ DataNode 配置
1. Confignode节点启动失败
- 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ - 步骤 2: 请查看启动日志，检查是否出现其他异常。
- 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
- 清理环境：
1. 结束所有 ConfigNode 和 DataNode 进程。
diff --git a/src/zh/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
b/src/zh/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
index 65269020..ae929485 100644
--- a/src/zh/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
+++ b/src/zh/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
@@ -101,87 +101,3 @@ static_configs:
[Grafana安装使用文档](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana从Prometheus查询数据并绘图的文档](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## 4. Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard`是 IoTDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到
Dashboard 的 Json文件。
-
-
-
-
-
-
-
-### 4.1 集群概览
-
-可以监控包括但不限于：
-- 集群总CPU核数、总内存空间、总硬盘空间
-- 集群包含多少个ConfigNode与DataNode
-- 集群启动时长
-- 集群写入速度
-- 集群各节点当前CPU、内存、磁盘使用率
-- 分节点的信息
-
-
-
-### 4.2 数据写入
-
-可以监控包括但不限于：
-- 写入平均耗时、耗时中位数、99%分位耗时
-- WAL文件数量与尺寸
-- 节点 WAL flush SyncBuffer 耗时
-
-
-
-### 4.3 数据查询
-
-可以监控包括但不限于：
-- 节点查询加载时间序列元数据耗时
-- 节点查询读取时间序列耗时
-- 节点查询修改时间序列元数据耗时
-- 节点查询加载Chunk元数据列表耗时
-- 节点查询修改Chunk元数据耗时
-- 节点查询按照Chunk元数据过滤耗时
-- 节点查询构造Chunk Reader耗时的平均值
-
-
-
-### 4.4 存储引擎
-
-可以监控包括但不限于：
-- 分类型的文件数量、大小
-- 处于各阶段的TsFile数量、大小
-- 各类任务的数量与耗时
-
-
-
-### 4.5 系统监控
-
-可以监控包括但不限于：
-- 系统内存、交换内存、进程内存
-- 磁盘空间、文件数、文件尺寸
-- JVM GC时间占比、分类型的GC次数、GC数据量、各年代的堆内存占用
-- 网络传输速率、包发送速率
-
-
-
-
-
-
-
-### 4.6 数据同步
-
-可以监控包括但不限于：
-- Pipe事件提交队列大小、未分配Pipe事件数。
-- Source队列未处理事件数、Source供给事件速率、Processor处理事件速率。
-- 各类Pipesink/source未传输事件数、Pipe connector传输事件速率。
-- Pipesink重试队列和pending handler数量、Pipesink压缩前后累计大小和压缩耗时、Pipesink 批量大小和批处理间隔分布。
-- Pipe内存占用和容量、Pipe phantom reference数量、linked TsFile数量和大小、Pipe发送TsFile读取磁盘字节数。
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
index b09ef486..e67d1ded 100644
---
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+++
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ AINode 安装包（`apache-iotdb-<version>-ainode-bin.zip`）解压后关键目
**准备工作：**
-* 获取官方发布的 SHA512 校验码：请联系商业支持获取
+* 获取官方发布的 SHA512 校验码
**校验步骤（以 linux 为例）：**
@@ -79,7 +79,7 @@
b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4
**注意事项：**
-* 若校验结果不一致，请联系商业支持重新获取安装包
+* 若校验结果不一致，请重新获取安装包
* 校验过程中若出现"文件不存在"提示，需检查文件路径是否正确或安装包是否完整下载
### 2.3 环境要求
@@ -119,7 +119,7 @@ AINode 支持修改一些必要的参数。可以在 `/IOTDB_AINODE_HOME/conf/io
若部署环境可联网且能连通 HuggingFace 环境，系统会自动拉取内置模型权重文件，可忽略本步骤。
-若为离线环境，联系商业支持获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。
+若为离线环境，需提前准备模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。
**NOTE：**注意目录层级，最终所有内置模型权重的父目录都是 `builtin `。
@@ -231,7 +231,7 @@ IoTDB> show cluster
* 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置
3. 更新内置模型权重（可选）
- *
若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至
`data/ainode/models/builtin` 目录
+ *
若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。需提前准备最新权重包，并将权重包替换至
`data/ainode/models/builtin` 目录
4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。
diff --git
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md
index 69f409db..ec1d7fe8 100644
---
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md
+++
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -127,7 +127,7 @@ AINode 支持修改一些必要的参数。可以在 `conf/iotdb-ainode.properti
> 仅离线环境，在线环境可忽略本步骤
>
-联系商业支持获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。
+需提前准备模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。
### 3.4 启动 AINode
diff --git
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index f8bb4bd7..811c0a0c 100644
---
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -476,7 +476,7 @@ remove datanode [datanode_id]
步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ 步骤 2: 请查看启动日志，检查是否出现其他异常。
步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
diff --git
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources_apache.md
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources_apache.md
index 685af9b5..9eae6bfb 100644
---
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources_apache.md
+++
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Database-Resources_apache.md
@@ -72,11 +72,11 @@
<td>48核</td>
<td>1</td>
<td>2</td>
- <td>请联系商业支持咨询</td>
+ <td>建议按需评估</td>
</tr>
<tr>
<td>1000w以上</td>
- <td colspan="4">请联系商业支持咨询</td>
+ <td colspan="4">建议按需评估</td>
</tr>
</tbody>
</table>
@@ -136,11 +136,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>请联系商业支持咨询</td>
+ <td>建议按需评估</td>
</tr>
<tr>
<td>1000w以上</td>
- <td colspan="4">请联系商业支持咨询</td>
+ <td colspan="4">建议按需评估</td>
</tr>
</tbody>
</table>
diff --git
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index 568d4ad4..064c2318 100644
---
a/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/zh/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -200,7 +200,7 @@ cd sbin
步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ 步骤 2: 请查看启动日志，检查是否出现其他异常。
步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
diff --git a/src/zh/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md
b/src/zh/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md
index abdd526d..42211f00 100644
--- a/src/zh/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md
+++ b/src/zh/UserGuide/Master/Tree/Tools-System/Monitor-Tool_apache.md
@@ -101,87 +101,3 @@ static_configs:
[Grafana安装使用文档](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana从Prometheus查询数据并绘图的文档](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## 4. Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard`是 IoTDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到
Dashboard 的 Json文件。
-
-
-
-
-
-
-
-### 4.1 集群概览
-
-可以监控包括但不限于：
-- 集群总CPU核数、总内存空间、总硬盘空间
-- 集群包含多少个ConfigNode与DataNode
-- 集群启动时长
-- 集群写入速度
-- 集群各节点当前CPU、内存、磁盘使用率
-- 分节点的信息
-
-
-
-### 4.2 数据写入
-
-可以监控包括但不限于：
-- 写入平均耗时、耗时中位数、99%分位耗时
-- WAL文件数量与尺寸
-- 节点 WAL flush SyncBuffer 耗时
-
-
-
-### 4.3 数据查询
-
-可以监控包括但不限于：
-- 节点查询加载时间序列元数据耗时
-- 节点查询读取时间序列耗时
-- 节点查询修改时间序列元数据耗时
-- 节点查询加载Chunk元数据列表耗时
-- 节点查询修改Chunk元数据耗时
-- 节点查询按照Chunk元数据过滤耗时
-- 节点查询构造Chunk Reader耗时的平均值
-
-
-
-### 4.4 存储引擎
-
-可以监控包括但不限于：
-- 分类型的文件数量、大小
-- 处于各阶段的TsFile数量、大小
-- 各类任务的数量与耗时
-
-
-
-### 4.5 系统监控
-
-可以监控包括但不限于：
-- 系统内存、交换内存、进程内存
-- 磁盘空间、文件数、文件尺寸
-- JVM GC时间占比、分类型的GC次数、GC数据量、各年代的堆内存占用
-- 网络传输速率、包发送速率
-
-
-
-
-
-
-
-### 4.6 数据同步
-
-可以监控包括但不限于：
-- Pipe事件提交队列大小、未分配Pipe事件数。
-- Source队列未处理事件数、Source供给事件速率、Processor处理事件速率。
-- 各类Pipesink/source未传输事件数、Pipe connector传输事件速率。
-- Pipesink重试队列和pending handler数量、Pipesink压缩前后累计大小和压缩耗时、Pipesink 批量大小和批处理间隔分布。
-- Pipe内存占用和容量、Pipe phantom reference数量、linked TsFile数量和大小、Pipe发送TsFile读取磁盘字节数。
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/src/zh/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md
b/src/zh/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md
index 93f7dc60..f9fd8c6d 100644
--- a/src/zh/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md
+++ b/src/zh/UserGuide/V1.2.x/Tools-System/Monitor-Tool.md
@@ -99,70 +99,3 @@ static_configs:
[Grafana安装使用文档](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana从Prometheus查询数据并绘图的文档](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-### Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard`是 IoTDB
企业版的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。
-
-
-
-
-
-
-#### 集群概览
-
-可以监控包括但不限于：
-- 集群总CPU核数、总内存空间、总硬盘空间
-- 集群包含多少个ConfigNode与DataNode
-- 集群启动时长
-- 集群写入速度
-- 集群各节点当前CPU、内存、磁盘使用率
-- 分节点的信息
-
-
-
-#### 数据写入
-
-可以监控包括但不限于：
-- 写入平均耗时、耗时中位数、99%分位耗时
-- WAL文件数量与尺寸
-- 节点 WAL flush SyncBuffer 耗时
-
-
-
-#### 数据查询
-
-可以监控包括但不限于：
-- 节点查询加载时间序列元数据耗时
-- 节点查询读取时间序列耗时
-- 节点查询修改时间序列元数据耗时
-- 节点查询加载Chunk元数据列表耗时
-- 节点查询修改Chunk元数据耗时
-- 节点查询按照Chunk元数据过滤耗时
-- 节点查询构造Chunk Reader耗时的平均值
-
-
-
-#### 存储引擎
-
-可以监控包括但不限于：
-- 分类型的文件数量、大小
-- 处于各阶段的TsFile数量、大小
-- 各类任务的数量与耗时
-
-
-
-#### 系统监控
-
-可以监控包括但不限于：
-- 系统内存、交换内存、进程内存
-- 磁盘空间、文件数、文件尺寸
-- JVM GC时间占比、分类型的GC次数、GC数据量、各年代的堆内存占用
-- 网络传输速率、包发送速率
-
-
-
-
-
-
-
diff --git
a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index 36bd73ac..b80e143e 100644
---
a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -414,7 +414,7 @@ sbin/remove-datanode.bat [datanode_id]
步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ 步骤 2: 请查看启动日志，检查是否出现其他异常。
步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
diff --git
a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index 7a2ed7a7..7305c372 100644
---
a/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/zh/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -176,7 +176,7 @@ cd sbin
步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ 步骤 2: 请查看启动日志，检查是否出现其他异常。
步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
diff --git a/src/zh/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md
b/src/zh/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md
index 3ef0730d..32c18a07 100644
--- a/src/zh/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md
+++ b/src/zh/UserGuide/V1.3.x/Tools-System/Monitor-Tool_apache.md
@@ -22,8 +22,6 @@
# Prometheus
-监控工具的部署可参考文档
[监控面板部署](../Deployment-and-Maintenance/Monitoring-panel-deployment.md) 章节。
-
## 监控指标的 Prometheus 映射关系
> 对于 Metric Name 为 name, Tags 为 K1=V1, ..., Kn=Vn 的监控指标有如下映射，其中 value 为具体值
@@ -101,70 +99,3 @@ static_configs:
[Grafana安装使用文档](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana从Prometheus查询数据并绘图的文档](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard`是 IoTDB
企业版的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。
-
-
-
-
-
-
-
-### 集群概览
-
-可以监控包括但不限于：
-- 集群总CPU核数、总内存空间、总硬盘空间
-- 集群包含多少个ConfigNode与DataNode
-- 集群启动时长
-- 集群写入速度
-- 集群各节点当前CPU、内存、磁盘使用率
-- 分节点的信息
-
-
-
-### 数据写入
-
-可以监控包括但不限于：
-- 写入平均耗时、耗时中位数、99%分位耗时
-- WAL文件数量与尺寸
-- 节点 WAL flush SyncBuffer 耗时
-
-
-
-### 数据查询
-
-可以监控包括但不限于：
-- 节点查询加载时间序列元数据耗时
-- 节点查询读取时间序列耗时
-- 节点查询修改时间序列元数据耗时
-- 节点查询加载Chunk元数据列表耗时
-- 节点查询修改Chunk元数据耗时
-- 节点查询按照Chunk元数据过滤耗时
-- 节点查询构造Chunk Reader耗时的平均值
-
-
-
-### 存储引擎
-
-可以监控包括但不限于：
-- 分类型的文件数量、大小
-- 处于各阶段的TsFile数量、大小
-- 各类任务的数量与耗时
-
-
-
-### 系统监控
-
-可以监控包括但不限于：
-- 系统内存、交换内存、进程内存
-- 磁盘空间、文件数、文件尺寸
-- JVM GC时间占比、分类型的GC次数、GC数据量、各年代的堆内存占用
-- 网络传输速率、包发送速率
-
-
-
-
-
-
diff --git
a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index 21e48c4b..0a130d29 100644
---
a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -201,7 +201,7 @@ cd sbin
->
出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系商业支持重新申请.
+>
出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件），其激活依赖于集群中其它Activate状态的ConfigNode。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请重新申请.
### 一键启停集群
@@ -406,7 +406,7 @@ remove datanode [datanode_id]
步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ 步骤 2: 请查看启动日志，检查是否出现其他异常。
步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
diff --git
a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index cae44bfc..e02ef2c9 100644
---
a/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/zh/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -172,7 +172,7 @@ cd sbin
->
出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件）。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系商业支持重新申请.
+>
出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件）。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请重新申请.
## 常见问题
@@ -180,7 +180,7 @@ cd sbin
步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ 步骤 2: 请查看启动日志，检查是否出现其他异常。
步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
diff --git a/src/zh/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md
b/src/zh/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md
index 871b61cb..4f0e850b 100644
--- a/src/zh/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md
+++ b/src/zh/UserGuide/dev-1.3/Tools-System/Monitor-Tool_apache.md
@@ -101,70 +101,3 @@ static_configs:
[Grafana安装使用文档](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana从Prometheus查询数据并绘图的文档](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard`是 IoTDB 的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到
Dashboard 的 Json文件。
-
-
-
-
-
-
-
-### 集群概览
-
-可以监控包括但不限于：
-- 集群总CPU核数、总内存空间、总硬盘空间
-- 集群包含多少个ConfigNode与DataNode
-- 集群启动时长
-- 集群写入速度
-- 集群各节点当前CPU、内存、磁盘使用率
-- 分节点的信息
-
-
-
-### 数据写入
-
-可以监控包括但不限于：
-- 写入平均耗时、耗时中位数、99%分位耗时
-- WAL文件数量与尺寸
-- 节点 WAL flush SyncBuffer 耗时
-
-
-
-### 数据查询
-
-可以监控包括但不限于：
-- 节点查询加载时间序列元数据耗时
-- 节点查询读取时间序列耗时
-- 节点查询修改时间序列元数据耗时
-- 节点查询加载Chunk元数据列表耗时
-- 节点查询修改Chunk元数据耗时
-- 节点查询按照Chunk元数据过滤耗时
-- 节点查询构造Chunk Reader耗时的平均值
-
-
-
-### 存储引擎
-
-可以监控包括但不限于：
-- 分类型的文件数量、大小
-- 处于各阶段的TsFile数量、大小
-- 各类任务的数量与耗时
-
-
-
-### 系统监控
-
-可以监控包括但不限于：
-- 系统内存、交换内存、进程内存
-- 磁盘空间、文件数、文件尺寸
-- JVM GC时间占比、分类型的GC次数、GC数据量、各年代的堆内存占用
-- 网络传输速率、包发送速率
-
-
-
-
-
-
diff --git
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
index e5772649..92b2a93b 100644
---
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+++
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ AINode 安装包（`apache-iotdb-<version>-ainode-bin.zip`）解压后关键目
**准备工作：**
-* 获取官方发布的 SHA512 校验码：请联系商业支持获取
+* 获取官方发布的 SHA512 校验码
**校验步骤（以 linux 为例）：**
@@ -79,7 +79,7 @@
b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4
**注意事项：**
-* 若校验结果不一致，请联系商业支持重新获取安装包
+* 若校验结果不一致，请重新获取安装包
* 校验过程中若出现"文件不存在"提示，需检查文件路径是否正确或安装包是否完整下载
### 2.3 环境要求
@@ -119,7 +119,7 @@ AINode 支持修改一些必要的参数。可以在 `/IOTDB_AINODE_HOME/conf/io
若部署环境可联网且能连通 HuggingFace 环境，系统会自动拉取内置模型权重文件，可忽略本步骤。
-若为离线环境，联系商业支持获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。
+若为离线环境，需提前准备模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。
**NOTE：**注意目录层级，最终所有内置模型权重的父目录都是 `builtin `。
@@ -231,7 +231,7 @@ IoTDB> show cluster
* 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置
3. 更新内置模型权重（可选）
- *
若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至
`data/ainode/models/builtin` 目录
+ *
若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history_apache.md)中同步。需提前准备最新权重包，并将权重包替换至
`data/ainode/models/builtin` 目录
4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。
diff --git
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
index 5badae7a..211e499d 100644
---
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
+++
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -127,7 +127,7 @@ AINode 支持修改一些必要的参数。可以在 `conf/iotdb-ainode.properti
> 仅离线环境，在线环境可忽略本步骤
>
-联系商业支持获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。
+需提前准备模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。
### 3.4 启动 AINode
diff --git
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index b0240d2c..c6e75bb8 100644
---
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -438,7 +438,7 @@ remove datanode [datanode_id]
1. Confignode节点启动失败
- 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ - 步骤 2: 请查看启动日志，检查是否出现其他异常。
- 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
- 清理环境：
diff --git
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md
index c1b64662..18a0703d 100644
---
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md
+++
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Database-Resources_apache.md
@@ -73,11 +73,11 @@
<td>48核</td>
<td>1</td>
<td>2</td>
- <td>请联系商业支持咨询</td>
+ <td>建议按需评估</td>
</tr>
<tr>
<td>1000w以上</td>
- <td colspan="4">请联系商业支持咨询</td>
+ <td colspan="4">建议按需评估</td>
</tr>
</tbody>
</table>
@@ -137,11 +137,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>请联系商业支持咨询</td>
+ <td>建议按需评估</td>
</tr>
<tr>
<td>1000w以上</td>
- <td colspan="4">请联系商业支持咨询</td>
+ <td colspan="4">建议按需评估</td>
</tr>
</tbody>
</table>
diff --git
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index e2f6a5b5..c5265c72 100644
---
a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -183,7 +183,7 @@ DataNode 配置
1. Confignode节点启动失败
- 步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- - 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ - 步骤 2: 请查看启动日志，检查是否出现其他异常。
- 步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
- 清理环境：
1. 结束所有 ConfigNode 和 DataNode 进程。
diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md
b/src/zh/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md
index 2b5cc468..42211f00 100644
--- a/src/zh/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md
+++ b/src/zh/UserGuide/latest-Table/Tools-System/Monitor-Tool_apache.md
@@ -101,87 +101,3 @@ static_configs:
[Grafana安装使用文档](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana从Prometheus查询数据并绘图的文档](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## 4. Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard`是 IoTDB
企业版的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。
-
-
-
-
-
-
-
-### 4.1 集群概览
-
-可以监控包括但不限于：
-- 集群总CPU核数、总内存空间、总硬盘空间
-- 集群包含多少个ConfigNode与DataNode
-- 集群启动时长
-- 集群写入速度
-- 集群各节点当前CPU、内存、磁盘使用率
-- 分节点的信息
-
-
-
-### 4.2 数据写入
-
-可以监控包括但不限于：
-- 写入平均耗时、耗时中位数、99%分位耗时
-- WAL文件数量与尺寸
-- 节点 WAL flush SyncBuffer 耗时
-
-
-
-### 4.3 数据查询
-
-可以监控包括但不限于：
-- 节点查询加载时间序列元数据耗时
-- 节点查询读取时间序列耗时
-- 节点查询修改时间序列元数据耗时
-- 节点查询加载Chunk元数据列表耗时
-- 节点查询修改Chunk元数据耗时
-- 节点查询按照Chunk元数据过滤耗时
-- 节点查询构造Chunk Reader耗时的平均值
-
-
-
-### 4.4 存储引擎
-
-可以监控包括但不限于：
-- 分类型的文件数量、大小
-- 处于各阶段的TsFile数量、大小
-- 各类任务的数量与耗时
-
-
-
-### 4.5 系统监控
-
-可以监控包括但不限于：
-- 系统内存、交换内存、进程内存
-- 磁盘空间、文件数、文件尺寸
-- JVM GC时间占比、分类型的GC次数、GC数据量、各年代的堆内存占用
-- 网络传输速率、包发送速率
-
-
-
-
-
-
-
-### 4.6 数据同步
-
-可以监控包括但不限于：
-- Pipe事件提交队列大小、未分配Pipe事件数。
-- Source队列未处理事件数、Source供给事件速率、Processor处理事件速率。
-- 各类Pipesink/source未传输事件数、Pipe connector传输事件速率。
-- Pipesink重试队列和pending handler数量、Pipesink压缩前后累计大小和压缩耗时、Pipesink 批量大小和批处理间隔分布。
-- Pipe内存占用和容量、Pipe phantom reference数量、linked TsFile数量和大小、Pipe发送TsFile读取磁盘字节数。
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
index e5772649..92b2a93b 100644
---
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
+++
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ AINode 安装包（`apache-iotdb-<version>-ainode-bin.zip`）解压后关键目
**准备工作：**
-* 获取官方发布的 SHA512 校验码：请联系商业支持获取
+* 获取官方发布的 SHA512 校验码
**校验步骤（以 linux 为例）：**
@@ -79,7 +79,7 @@
b39039a1235a86bc3ce3df0a102efa215e281b5839683ccaf47883b390af4e686f99e6980a24a9d4
**注意事项：**
-* 若校验结果不一致，请联系商业支持重新获取安装包
+* 若校验结果不一致，请重新获取安装包
* 校验过程中若出现"文件不存在"提示，需检查文件路径是否正确或安装包是否完整下载
### 2.3 环境要求
@@ -119,7 +119,7 @@ AINode 支持修改一些必要的参数。可以在 `/IOTDB_AINODE_HOME/conf/io
若部署环境可联网且能连通 HuggingFace 环境，系统会自动拉取内置模型权重文件，可忽略本步骤。
-若为离线环境，联系商业支持获取模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。
+若为离线环境，需提前准备模型权重文件夹，并放置到`/IOTDB_AINODE_HOME/data/ainode/models/builtin` 目录下。
**NOTE：**注意目录层级，最终所有内置模型权重的父目录都是 `builtin `。
@@ -231,7 +231,7 @@ IoTDB> show cluster
* 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置
3. 更新内置模型权重（可选）
- *
若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至
`data/ainode/models/builtin` 目录
+ *
若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history_apache.md)中同步。需提前准备最新权重包，并将权重包替换至
`data/ainode/models/builtin` 目录
4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。
diff --git
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md
index ed5592f0..66a3c03e 100644
---
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md
+++
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -126,7 +126,7 @@ AINode 支持修改一些必要的参数。可以在 `conf/iotdb-ainode.properti
> 仅离线环境，在线环境可忽略本步骤
>
-联系商业支持获取模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。
+需提前准备模型权重文件，并放置到/IOTDB_AINODE_HOME/data/ainode/models/weights/目录下。
### 3.4 启动 AINode
diff --git
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index f8bb4bd7..811c0a0c 100644
---
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -476,7 +476,7 @@ remove datanode [datanode_id]
步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ 步骤 2: 请查看启动日志，检查是否出现其他异常。
步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
diff --git
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Database-Resources_apache.md
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Database-Resources_apache.md
index 685af9b5..9eae6bfb 100644
---
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Database-Resources_apache.md
+++
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Database-Resources_apache.md
@@ -72,11 +72,11 @@
<td>48核</td>
<td>1</td>
<td>2</td>
- <td>请联系商业支持咨询</td>
+ <td>建议按需评估</td>
</tr>
<tr>
<td>1000w以上</td>
- <td colspan="4">请联系商业支持咨询</td>
+ <td colspan="4">建议按需评估</td>
</tr>
</tbody>
</table>
@@ -136,11 +136,11 @@
<td>128G</td>
<td>1</td>
<td>2</td>
- <td>请联系商业支持咨询</td>
+ <td>建议按需评估</td>
</tr>
<tr>
<td>1000w以上</td>
- <td colspan="4">请联系商业支持咨询</td>
+ <td colspan="4">建议按需评估</td>
</tr>
</tbody>
</table>
diff --git
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index 568d4ad4..064c2318 100644
---
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -200,7 +200,7 @@ cd sbin
步骤 1: 请查看启动日志，检查是否修改了某些首次启动后不可改的参数。
- 步骤 2: 请查看启动日志，检查是否出现其他异常。日志中若存在异常现象，请联系商业支持咨询解决方案。
+ 步骤 2: 请查看启动日志，检查是否出现其他异常。
步骤 3: 如果是首次部署或者数据可删除，也可按下述步骤清理环境，重新部署后，再次启动。
diff --git a/src/zh/UserGuide/latest/Tools-System/Monitor-Tool_apache.md
b/src/zh/UserGuide/latest/Tools-System/Monitor-Tool_apache.md
index 065bd3cf..28ce6587 100644
--- a/src/zh/UserGuide/latest/Tools-System/Monitor-Tool_apache.md
+++ b/src/zh/UserGuide/latest/Tools-System/Monitor-Tool_apache.md
@@ -101,87 +101,3 @@ static_configs:
[Grafana安装使用文档](https://grafana.com/docs/grafana/latest/getting-started/getting-started/)
[Grafana从Prometheus查询数据并绘图的文档](https://prometheus.io/docs/visualization/grafana/#grafana-support-for-prometheus)
-
-## 4. Apache IoTDB Dashboard
-
-`Apache IoTDB Dashboard`是 IoTDB
企业版的配套产品，支持统一集中式运维管理，可通过一个监控面板监控多个集群。你可以联系商务获取到 Dashboard 的 Json文件。
-
-
-
-
-
-
-
-### 4.1 集群概览
-
-可以监控包括但不限于：
-- 集群总CPU核数、总内存空间、总硬盘空间
-- 集群包含多少个ConfigNode与DataNode
-- 集群启动时长
-- 集群写入速度
-- 集群各节点当前CPU、内存、磁盘使用率
-- 分节点的信息
-
-
-
-### 4.2 数据写入
-
-可以监控包括但不限于：
-- 写入平均耗时、耗时中位数、99%分位耗时
-- WAL文件数量与尺寸
-- 节点 WAL flush SyncBuffer 耗时
-
-
-
-### 4.3 数据查询
-
-可以监控包括但不限于：
-- 节点查询加载时间序列元数据耗时
-- 节点查询读取时间序列耗时
-- 节点查询修改时间序列元数据耗时
-- 节点查询加载Chunk元数据列表耗时
-- 节点查询修改Chunk元数据耗时
-- 节点查询按照Chunk元数据过滤耗时
-- 节点查询构造Chunk Reader耗时的平均值
-
-
-
-### 4.4 存储引擎
-
-可以监控包括但不限于：
-- 分类型的文件数量、大小
-- 处于各阶段的TsFile数量、大小
-- 各类任务的数量与耗时
-
-
-
-### 4.5 系统监控
-
-可以监控包括但不限于：
-- 系统内存、交换内存、进程内存
-- 磁盘空间、文件数、文件尺寸
-- JVM GC时间占比、分类型的GC次数、GC数据量、各年代的堆内存占用
-- 网络传输速率、包发送速率
-
-
-
-
-
-
-
-### 4.6 数据同步
-
-可以监控包括但不限于：
-- Pipe事件提交队列大小、未分配Pipe事件数。
-- Source队列未处理事件数、Source供给事件速率、Processor处理事件速率。
-- 各类Pipesink/source未传输事件数、Pipe connector传输事件速率。
-- Pipesink重试队列和pending handler数量、Pipesink压缩前后累计大小和压缩耗时、Pipesink 批量大小和批处理间隔分布。
-- Pipe内存占用和容量、Pipe phantom reference数量、linked TsFile数量和大小、Pipe发送TsFile读取磁盘字节数。
-
-
-
-
-
-
-
-
\ No newline at end of file
