You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iotdb.apache.org by ha...@apache.org on 2022/11/23 06:44:38 UTC
[iotdb] branch master updated: remove node tool of 0.13 cluster (#8109)
This is an automated email from the ASF dual-hosted git repository.
haonan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/iotdb.git
The following commit(s) were added to refs/heads/master by this push:
new d871670848 remove node tool of 0.13 cluster (#8109)
d871670848 is described below
commit d871670848797b3d784f41c61903930a1c237dc3
Author: Jialin Qiao <qj...@mails.tsinghua.edu.cn>
AuthorDate: Wed Nov 23 14:44:32 2022 +0800
remove node tool of 0.13 cluster (#8109)
---
docs/UserGuide/Maintenance-Tools/NodeTool.md | 297 ------------------------
docs/zh/UserGuide/Maintenance-Tools/NodeTool.md | 293 -----------------------
site/src/main/.vuepress/config.js | 4 +-
3 files changed, 1 insertion(+), 593 deletions(-)
diff --git a/docs/UserGuide/Maintenance-Tools/NodeTool.md b/docs/UserGuide/Maintenance-Tools/NodeTool.md
deleted file mode 100644
index e6ea917ed3..0000000000
--- a/docs/UserGuide/Maintenance-Tools/NodeTool.md
+++ /dev/null
@@ -1,297 +0,0 @@
-<!--
-
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
-
--->
-
-# Introduction
-IoTDB cluster version provides nodetool, a shell tool for users to monitor the working status of the specified cluster.
-Users can obtain the status of the cluster by running a variety of instructions.
-
-The following describes the usage and examples of each instruction,
-where $IOTDB_CLUSTER_HOME indicates the path of the distributed IoTDB installation directory.
-
-# Prerequisites
-To use the nodetool, you need to enable JMX service. Please refer to [JMX tool](JMX-Tool.md) for details.
-
-# Instructions
-## Get Started
-The nodetool shell tool startup script is located at $IOTDB_CLUSTER_HOME/sbin folder,
-you can specify the IP address and port of the cluster during startup.
-
-IP is the IP (or hostname) of the node that you expect to connect to,
-and port is the JMX service port specified when the IoTDB cluster is started.
-
-The default values are `127.0.0.1` and `31999`, respectively.
-
-If you need to monitor the remote cluster or modify the JMX service port number,
-set the actual IP and port with the `-h` and `-p` options.
-
-When JMX authentication service is enabled, the username and password of JMX service should be specified.
-The default values are `iotdb` and `passw!d`, respectively. Please use the start parameters `-u` and `-pw`
-to specify the username and password of the JMX service.
-
-## Explains
-In a distributed system, a node is identified by node IP, metadata port, data port and cluster port \<IP:METAPORT:DATAPORT:CLUSTERPORT>.
-### Show The Ring Of Node
-Distributed IoTDB uses consistent hash to support data distribution.
-
-You can know each node in the cluster by command `ring`, which prints node ring information.
-
-1.Input
-> ring
-
-2.Output
-
-> The output is a multi-line string, and each line of string is a key value pair,
-> where the key represents the node identifier, and the value represents the node (IP:METAPORT:DATAPORT:CLUSTERPORT), the format is \<key -> value>.
-
-3.Examples
-
-> Suppose that the current cluster runs on three nodes: 127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668, and 127.0.0.1:9007:40014:6669.
-
-Examples of input instructions for different systems are as follows:
-
-Linux and MacOS：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 ring
-```
-
-Windows：
-
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 ring
-```
-
-Press enter to execute the command.
-
-The output of the example instruction is as follows:
-```
-Node Identifier Node
-330411070 -> 127.0.0.1:9003:40010:6667
-330454032 -> 127.0.0.1:9005:40012:6668
-330496472 -> 127.0.0.1:9007:40014:6669
-```
-
-The above output shows that there are three nodes in the current cluster,
-and the output results are ordered by their identifier ascendant.
-
-### Query data partition and metadata partition
-The time series metadata of distributed iotdb is divided into multiple data groups according to their databases,
-in which the database and data partition are many to one relationship.
-
-That is, all metadata of a database only exists in the same data group,
-and a data group may contain multiple databases.
-
-The data is divided into multiple data groups according to its database and timestamp,
-and the time partition granularity is decided by a configuration (currently unavailable).
-
-The data partition is composed of several replica nodes to ensure high availability of data,
-and one of the nodes plays the role of leader.
-
-Through this instruction, the user can know the metadata of a certain path,
- and the nodes under which the data is stored.
-
-1.Input
-> The instruction for querying data partition information is `partition`.
-> The parameters are described as follows:
-
-|Parameter|Description|Examples|
-| --- | --- | --- |
-|-m | --metadata Query metadata partition, by default only query data partition| -m |
-|-path | --path Required parameter, the path to be queried. If the path has no corresponding database, the query fails| -path root.guangzhou.d1|
-|-st | --StartTime The system uses the current partition time by default| -st 1576724778159 |
-|-et | --EndTime It is used when querying data partition.<br>The end time is the current system time by default. <br> If the end time is less than the start time, the end time is the start time by default|-et 1576724778159 |
-
-2.Output
-
-> The output is a multi-line string, and each line of string is a key-value pair, where the key represents the partition,
-> and the value represents the data group in the format of \< key -> value>.
-
-3.Examples
-
-> Suppose that the current cluster runs on three nodes: 127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668, and 127.0.0.1:9007:40014:6669.
->
-> The number of copies is 2 and there are 3 databases:{ root.beijing , root.shanghai , root.guangzhou}.
-
-+ Partition of query data (default time range, time partition interval is one day)
-
-Linux and MacOS：
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1
-```
-Windows：
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1
-```
-
-Press enter to execute the command.
-
-The output of the example instruction is as follows:
-```
-DATA<root.guangzhou.d1, 1576723735188, 1576723735188> -> [127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668]
-```
-
-+ Partition of query data (specified time range, time partition interval is one day)
-
-
-Linux and MacOS：
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1 -st 1576624778159 -et 1576724778159
-```
-Windows：
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1 -st 1576624778159 -et 1576724778159
-```
-
-Press enter to execute the command.
-
-The output of the example instruction is as follows:
-```
-DATA<root.guangzhou.d1, 1576627200000, 1576713599999> -> [127.0.0.1:9007:40014:6669, 127.0.0.1:9003:40010:6667]
-DATA<root.guangzhou.d1, 1576713600000, 1576724778159> -> [127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668]
-DATA<root.guangzhou.d1, 1576624778159, 1576627199999> -> [127.0.0.1:9005:40012:6668, 127.0.0.1:9007:40014:6669]
-```
-
-+ Query metadata partition
-
-Linux and MacOS：
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1 -m
-```
-Windows：
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1 -m
-```
-
-Press enter to execute the command.
-
-The output of the example instruction is as follows:
-```
-DATA<root.guangzhou.d1, 1576723735188, 1576723735188> -> [127.0.0.1:9003:40010, 127.0.0.1:9004:40011]
-```
-The above output shows that the data group to which root.guangzhou.d1 belongs contains two nodes,
-of which 127.0.0.1:9003:40010 is the header node.
-
-
-### Query the number of slots managed by the node
-Distributed IoTDB divides data into a fixed number of (10000 by default) slots,
-and the leader of the cluster management group divides the slots among data groups.
-
-Through this instruction, you can know the number of slots managed by each data group.
-
-1. Input
-> The command to query the data partition information corresponding to the node is `host`.
->
-> The parameters are described as follows:
-
-|Parameter|Description|Examples|
-|---|---|---|
-|-a or --all |Query the number of slots managed by all data groups. By default only data groups of the query node are shown|-a|
-
-2.Output
-
-> The output is a multi-line string, in which each line is a key-value pair, where the key represents the data group,
-> and the value represents the number of slots managed, and the format is \<key -> value>.
-
-3.Examples
-
-> Suppose that the current cluster runs on three nodes: 127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668, and 127.0.0.1:9007:40014:6669,
-> and the number of copies is 2.
-
-+ Default Partition Group
-
-Linux and MacOS：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 host
-```
-
-Windows：
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 host
-```
-
-Press enter to execute the command.
-
-The output of the example instruction is as follows:
-```
-Raft group Slot Number
-(127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668) -> 3333
-(127.0.0.1:9007:40014:6669, 127.0.0.1:9003:40010:6667) -> 3334
-```
-+ All Partition Groups
-
-Linux and MacOS：
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 host -a
-```
-Windows：
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 host -a
-```
-
-Press enter to execute the command.
-
-The output of the example instruction is as follows:
-```
-Raft group Slot Number
-(127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668) -> 3333
-(127.0.0.1:9005:40012:6668, 127.0.0.1:9007:40014:6669) -> 3333
-(127.0.0.1:9007:40014:6669, 127.0.0.1:9003:40010:6667) -> 3334
-```
-
-### Query node status
-Distributed IoTDB contains multiple nodes.
-For any node, there is a possibility that it cannot provide services normally due to network or hardware problems.
-
-Through this instruction, you can know the current status of all nodes in the cluster.
-
-1.Input
-> status
-
-2.Output
-> The output is a multi-line string, where each line is a key-value pair, where the key represents the node (IP: METAPORT:DATAPORT),
-> the value indicates the status of the node, "on" is normal, "off" is abnormal, and the format is \< key -> value>.
-
-3.Examples
-> Suppose that the current cluster runs on three nodes: 127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668, and 127.0.0.1:9007:40014:6669,
-> and the number of copies is 2.
-
-Linux and MacOS：
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 status
-```
-Windows：
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 status
-```
-
-Press enter to execute the command.
-
-The output of the example instruction is as follows:
-```
-Node Status
-127.0.0.1:9003:40010:6667 -> on
-127.0.0.1:9005:40012:6668 -> off
-127.0.0.1:9007:40014:6669 -> on
-
-```
-The above output indicates that 127.0.0.1:9003:40010:6667 nodes and 127.0.0.1:9007:40014:6669 nodes are in normal state,
-and 127.0.0.1:9005:40012:6668 nodes cannot provide services.
diff --git a/docs/zh/UserGuide/Maintenance-Tools/NodeTool.md b/docs/zh/UserGuide/Maintenance-Tools/NodeTool.md
deleted file mode 100644
index d05e8e9107..0000000000
--- a/docs/zh/UserGuide/Maintenance-Tools/NodeTool.md
+++ /dev/null
@@ -1,293 +0,0 @@
-<!--
-
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
-
--->
-
-# 工具介绍
-
-IoTDB 集群版为您提供了 NodeTool Shell 工具用于监控指定集群的工作状态，您可以通过运行多种指令获取集群各项状态。
-
-下面具体介绍每个指令的使用方式及示例，其中 $IOTDB_CLUSTER_HOME 表示 IoTDB 分布式的安装目录所在路径。
-
-# 前提条件
-使用 NodeTool 需要开启 JMX 服务，具体请参考 [JMX Tool](JMX-Tool.md)。
-
-# 使用说明
-
-## 运行方式
-
-NodeTool Shell 工具启动脚本位于 $IOTDB_CLUSTER_HOME/sbin 文件夹下，启动时可以指定集群运行的 IP 和 PORT。
-其中 IP 为您期望连接的节点的 IP，PORT 为 IoTDB 集群启动时指定的 JMX 服务端口号，分别默认为`127.0.0.1`和`31999`。
-
-如果您需要监控远程集群或修改了 JMX 服务端口号，请通过启动参数`-h`和`-p`项来使用实际的 IP 和 PORT。
-
-对于开启了 JMX 鉴权服务的，启动时候需要指定 JMX 服务的用户名和密码，默认分别为`iotdb`和`passw!d`，请通过启动参数`-u` 和`-pw`
-项来指定 JMX 服务的用户名和密码。
-
-## 指令说明
-在分布式系统中，一个节点由节点 IP，元数据端口，数据端口和服务端口来标识，即 Node\<IP:METAPORT:DATAPORT:CLUSTERPORT>。
-
-### 展示节点环
-
-IoTDB 集群版采用一致性哈希的方式实现数据分布，用户可以通过打印哈希环信息了解每个节点在环中的位置。
-
-1. 输入
-
-> 打印哈希环的指令为 ring
-
-2. 输出
-
-> 输出为多行字符串，每行字符串为一个键值对，其中键表示节点标识，值表示节点 (IP:METAPORT:DATAPORT:CLUSTERPORT)，格式为、<key -> value>。
-
-3. 示例
-
-> 假设当前集群运行在 127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668 和 127.0.0.1:9007:40014:6669 三个节点上。
-不同系统的输入指令示例如下：
-
-Linux 系统与 MacOS 系统：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 ring
-```
-
-Windows 系统：
-
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 ring
-```
-
-回车后即可执行指令。示例指令的输出如下：
-```
-Node Identifier Node
-330411070 -> 127.0.0.1:9003:40010:6667
-330454032 -> 127.0.0.1:9005:40012:6668
-330496472 -> 127.0.0.1:9007:40014:6669
-```
-
-上述输出表示当前集群共有 3 个节点，按照节点标识从小到大输出结果。
-
-### 查询数据分区和元数据分区
-
-IoTDB 集群版的时间序列元数据按照 database 分给多个数据组，其中 database 和数据组为多对一的关系，
-即同一个 database 的时间序列元数据只存在于同一个数据组，一个数据组可能包含多个 database 的时间序列元数据；
-
-数据按照 database 和其时间戳分给不同数据组，时间分区粒度默认为一天。
-
-数据组由多个节点组成，节点数量为副本数，保证数据高可用，其中某一个节点担任 Leader 的角色。
-
-通过该指令，用户可以获知某个路径下的元数据或数据具体存储在哪些节点下。
-
-1. 输入
-
-> 查询数据分区信息的指令为 partition，参数具体说明如下：
-
-|参数名|参数说明|示例|
-| --- | --- | --- |
-|-m | --metadata 查询元数据分区，默认为查询数据分区| -m |
-|-path | --path 必要参数，需要查询的路径，若该路径无对应的 database，则查询失败| -path root.guangzhou.d1|
-|-st | --StartTime 查询数据分区时使用，起始时间，默认为系统当前时间| -st 1576724778159 |
-|-et | --EndTime 查询数据分区时使用，终止时间，默认为系统当前时间。若终止时间小于起始时间，则终止时间默认为起始时间| -et 1576724778159 |
-
-2. 输出
-
-> 输出为多行字符串，每行字符串为一个键值对，其中键表示分区，值表示数据组，格式为、<key -> value>。
-
-3. 示例
-
-> 假设当前集群运行在 127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668 和 127.0.0.1:9007:40014:6669 三个节点上。
-> 副本数为 2，共有 3 个 database：{root.beijing、root.shanghai、root.guangzhou}。
-
-+ 查询数据的分区（默认时间范围，时间按天分区）
-
-不同系统的输入指令示例如下：
-
-Linux 系统与 MacOS 系统：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1
-```
-
-Windows 系统：
-
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1
-```
-回车后即可执行指令。示例指令的输出如下：
-
-```
-DATA<root.guangzhou.d1, 1576723735188, 1576723735188> -> [127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668]
-```
-
-+ 查询数据的分区（指定时间范围，时间按天分区）
-
-不同系统的输入指令示例如下：
-
-Linux 系统与 MacOS 系统：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1 -st 1576624778159 -et 1576724778159
-```
-
-Windows 系统：
-
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1 -st 1576624778159 -et 1576724778159
-```
-
-回车后即可执行指令。示例指令的输出如下：
-
-```
-DATA<root.guangzhou.d1, 1576627200000, 1576713599999> -> [127.0.0.1:9007:40014:6669, 127.0.0.1:9003:40010:6667]
-DATA<root.guangzhou.d1, 1576713600000, 1576724778159> -> [127.0.0.1:9003:40010:6668, 127.0.0.1:9005:40012:6668]
-DATA<root.guangzhou.d1, 1576624778159, 1576627199999> -> [127.0.0.1:9005:40012:6667, 127.0.0.1:9007:40014:6669]
-```
-
-+ 查询元数据分区
-
-不同系统的输入指令示例如下：
-
-Linux 系统与 MacOS 系统：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1 -m
-```
-
-Windows 系统：
-
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 partition -path root.guangzhou.d1 -m
-```
-
-回车后即可执行指令。示例指令的输出如下：
-
-```
-DATA<root.guangzhou.d1, 1576723735188, 1576723735188> -> [127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668]
-```
-上述输出表示 root.t1.d1 所属的数据分区包含 2 个节点，其中 127.0.0.1:9003:40010:6667 为 header 节点。
-
-### 查询节点管理的槽数
-
-IoTDB 集群版将哈希环划分为固定数量（默认 10000) 个槽，并由集群管理组（元数据组）的 leader 将槽划分各个数据组。通过该指令，用户可以获知数据组管理的槽数。
-
-1. 输入
-
-> 查询节点对应数据分区信息的指令为 host，参数具体说明如下：
-
-|参数名|参数说明|示例|
-|---|---|---|
-|-a --all |查询所有数据组管理的槽数，默认为查询的节点所在的数据组|-a|
-
-2. 输出
-
-> 输出为多行字符串，其中每行字符串为一个键值对，其中键表示数据组，值表示管理的槽数，格式为、<key -> value>。
-
-3. 示例
-
-> 假设当前集群运行在 127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668 和 127.0.0.1:9007:40014:6669 三个节点上，副本数为 2。
-
-+ 默认节点所在分区
-
-不同系统的输入指令示例如下：
-
-Linux 系统与 MacOS 系统：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 host
-```
-
-Windows 系统：
-
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 host
-```
-
-回车后即可执行指令。示例指令的输出如下：
-
-```
-Raft group Slot Number
-(127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668) -> 3333
-(127.0.0.1:9007:40014:6669, 127.0.0.1:9003:40010:6667) -> 3334
-```
-
-+ 所有分区
-
-不同系统的输入指令示例如下：
-
-Linux 系统与 MacOS 系统：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 host -a
-```
-
-Windows 系统：
-
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 host -a
-```
-
-回车后即可执行指令。示例指令的输出如下：
-
-```
-Raft group Slot Number
-(127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668) -> 3333
-(127.0.0.1:9005:40012:6668, 127.0.0.1:9007:40014:6669) -> 3333
-(127.0.0.1:9007:40014:6669, 127.0.0.1:9003:40010:6667) -> 3334
-```
-
-### 查询节点状态
-
-IoTDB 集群版包含多个节点，对于任意节点都存在因为网络、硬件等问题导致无法正常提供服务的可能。
-
-通过该指令，用户即可获知集群中所有节点当前的状态。
-
-1. 输入
-
-> 查询节点状态的指令为 status，无其他参数。
-
-2. 输出
-
-> 输出为多行字符串，其中每行字符串为一个键值对，其中键表示节点 (IP:METAPORT:DATAPORT)，
-> 值表示该节点的状态，“on”为正常，“off”为不正常，格式为、<key -> value>。
-
-3. 示例
-> 假设当前集群运行在 127.0.0.1:9003:40010:6667, 127.0.0.1:9005:40012:6668 和 127.0.0.1:9007:40014:6669 三个节点上，副本数为 2。
-
-不同系统的输入指令示例如下：
-
-Linux 系统与 MacOS 系统：
-
-```
-Shell > ./sbin/nodetool.sh -h 127.0.0.1 -p 31999 status
-```
-
-Windows 系统：
-
-```
-Shell > .\sbin\nodetool.bat -h 127.0.0.1 -p 31999 status
-```
-
-回车后即可执行指令。示例指令的输出如下：
-
-```
-Node Status
-127.0.0.1:9003:40010:6667 -> on
-127.0.0.1:9005:40012:6668 -> off
-127.0.0.1:9007:40014:6669 -> on
-```
-上述输出表示 127.0.0.1:9003:40010:6667 节点和 127.0.0.1:9007:40014:6669 节点状态正常，127.0.0.1:9005:40012:6668 节点无法提供服务。
diff --git a/site/src/main/.vuepress/config.js b/site/src/main/.vuepress/config.js
index 89f62f8c95..5a94c1ba85 100644
--- a/site/src/main/.vuepress/config.js
+++ b/site/src/main/.vuepress/config.js
@@ -965,7 +965,6 @@ var config = {
['Maintenance-Tools/Log-Tool','Log Tool'],
['Maintenance-Tools/JMX-Tool','JMX Tool'],
['Maintenance-Tools/MLogParser-Tool','MLogParser Tool'],
- ['Maintenance-Tools/NodeTool','Node Tool'],
['Maintenance-Tools/TsFile-Split-Tool','TsFile Split Tool'],
['Maintenance-Tools/TsFile-Load-Export-Tool','TsFile Load Export Tool'],
['Maintenance-Tools/CSV-Tool','CSV Load Export Tool'],
@@ -1854,7 +1853,7 @@ var config = {
]
},
{
- title: '数据写入（更新）',
+ title: '数据写入（数据更新）',
sidebarDepth: 1,
children: [
['Write-Data/Write-Data','CLI 工具写入'],
@@ -1949,7 +1948,6 @@ var config = {
['Maintenance-Tools/Log-Tool','日志工具'],
['Maintenance-Tools/JMX-Tool','JMX 工具'],
['Maintenance-Tools/MLogParser-Tool','Mlog解析工具'],
- ['Maintenance-Tools/NodeTool','节点工具'],
['Maintenance-Tools/TsFile-Split-Tool','TsFile 拆分工具'],
['Maintenance-Tools/TsFile-Load-Export-Tool','TsFile 导入导出工具'],
['Maintenance-Tools/CSV-Tool','CSV 导入导出工具'],