This is an automated email from the ASF dual-hosted git repository.
caogaofei 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 ffe28e8 Fix issue with modifying deployment documents
ffe28e8 is described below
commit ffe28e81762560403b70e638d679ccc4fa45b8aa
Author: W1y1r <[email protected]>
AuthorDate: Mon Sep 23 09:39:40 2024 +0800
Fix issue with modifying deployment documents
---
.../Cluster-Deployment_apache.md | 8 ++++++++
.../Cluster-Deployment_timecho.md | 15 ++++++++++++++-
.../Stand-Alone-Deployment_apache.md | 8 ++++++++
.../Stand-Alone-Deployment_timecho.md | 17 +++++++++++++++--
.../Cluster-Deployment_apache.md | 8 ++++++++
.../Cluster-Deployment_timecho.md | 17 +++++++++++++++--
.../Stand-Alone-Deployment_apache.md | 8 ++++++++
.../Stand-Alone-Deployment_timecho.md | 17 +++++++++++++++--
.../Cluster-Deployment_apache.md | 8 ++++++++
.../Cluster-Deployment_timecho.md | 18 ++++++++++++++++--
.../Stand-Alone-Deployment_apache.md | 8 ++++++++
.../Stand-Alone-Deployment_timecho.md | 17 ++++++++++++++++-
.../Cluster-Deployment_apache.md | 8 ++++++++
.../Cluster-Deployment_timecho.md | 18 ++++++++++++++++--
.../Stand-Alone-Deployment_apache.md | 8 ++++++++
.../Stand-Alone-Deployment_timecho.md | 16 +++++++++++++++-
16 files changed, 186 insertions(+), 13 deletions(-)
diff --git
a/src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index e10df50..fbc0c86 100644
---
a/src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -40,6 +40,12 @@ This section will take the IoTDB classic cluster deployment
architecture 3C3D (3
4. Whether in linux or windows, ensure that the IoTDB installation path does
not contain Spaces and Chinese characters to avoid software exceptions.
+5. Please note that when installing and deploying IoTDB, it is necessary to
use the same user for operations. You can:
+- Using root user (recommended): Using root user can avoid issues such as
permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for
start, stop and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute
commands with root privileges, which may cause confusion or security issues.
+
## Preparation Steps
1. Prepare the IoTDB database installation
package:：apache-iotdb-{version}-all-bin.zip（Please refer to the installation
package for
details：[IoTDB-Package](../Deployment-and-Maintenance/IoTDB-Package_apache.md)）
@@ -125,6 +131,8 @@ Open DataNode Configuration File
`./conf/iotdb-system.properties`,Set the follow
| dn_schema_region_consensus_port | The port used by DataNode for metadata
replica consensus protocol communication | 10760 | 10760
| 10760 | 10760 |
10760 | Cannot be modified after initial startup |
| dn_seed_config_node | The ConfigNode address that the node
connects to when registering to join the cluster, i.e. `cn_internal-address:
cn_internal_port` | 127.0.0.1:10710 | The first CongfigNode's
cn_internal-address: cn_internal_port | iotdb-1:10710 | iotdb-1:10710 |
iotdb-1:10710 | Cannot be modified after initial startup |
+> ❗️Attention: Editors such as VSCode Remote do not have automatic
configuration saving function. Please ensure that the modified files are saved
persistently, otherwise the configuration items will not take effect
+
### Start ConfigNode
Start the first confignode of IoTDB-1 first, ensuring that the seed confignode
node starts first, and then start the second and third confignode nodes in
sequence
diff --git
a/src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
b/src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
index 3bde0f2..37f229d 100644
---
a/src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
+++
b/src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
@@ -39,7 +39,13 @@ This section describes how to manually deploy an instance
that includes 3 Config
4. Whether in linux or windows, ensure that the IoTDB installation path does
not contain Spaces and Chinese characters to avoid software exceptions.
-5. It is recommended to deploy a monitoring panel, which can monitor important
operational indicators and keep track of database operation status at any time.
The monitoring panel can be obtained by contacting the business department,The
steps for deploying a monitoring panel can refer to:[Monitoring Panel
Deployment](.\Monitoring-panel-deployment.md)
+5. Please note that when installing and deploying IoTDB (including activating
and using software), it is necessary to use the same user for operations. You
can:
+- Using root user (recommended): Using root user can avoid issues such as
permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for
start, activation, stop, and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute
commands with root privileges, which may cause confusion or security issues.
+
+6. It is recommended to deploy a monitoring panel, which can monitor important
operational indicators and keep track of database operation status at any time.
The monitoring panel can be obtained by contacting the business department,The
steps for deploying a monitoring panel can refer to:[Monitoring Panel
Deployment](.\Monitoring-panel-deployment.md)
## Preparation Steps
@@ -125,6 +131,8 @@ Open DataNode Configuration File
`./conf/iotdb-system.properties`,Set the follow
| dn_schema_region_consensus_port | The port used by DataNode for metadata
replica consensus protocol communication | 10760 | 10760
| 10760 | 10760 |
10760 | Cannot be modified after initial startup |
| dn_seed_config_node | The ConfigNode address that the node
connects to when registering to join the cluster, i.e. `cn_internal-address:
cn_internal_port` | 127.0.0.1:10710 | The first CongfigNode's
cn_internal-address: cn_internal_port | iotdb-1:10710 | iotdb-1:10710 |
iotdb-1:10710 | Cannot be modified after initial startup |
+> ❗️Attention: Editors such as VSCode Remote do not have automatic
configuration saving function. Please ensure that the modified files are saved
persistently, otherwise the configuration items will not take effect
+
### Start ConfigNode
Start the first confignode of IoTDB-1 first, ensuring that the seed confignode
node starts first, and then start the second and third confignode nodes in
sequence
@@ -335,3 +343,8 @@ sbin/remove-datanode.sh [datanode_id]
#Windows
sbin/remove-datanode.bat [datanode_id]
```
+
+## Common Problem
+1. Multiple prompts indicating activation failure during deployment process
+ - Use the `ls -al` command: Use the `ls -al` command to check if the owner
information of the installation package root directory is the current user.
+ - Check activation directory: Check all files in the `./activation`
directory and whether the owner information is the current user.
\ No newline at end of file
diff --git
a/src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index 7749d3f..4e1f146 100644
---
a/src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -34,6 +34,12 @@
4. Whether in linux or windows, ensure that the IoTDB installation path does
not contain Spaces and Chinese characters to avoid software exceptions.
+5. Please note that when installing and deploying IoTDB, it is necessary to
use the same user for operations. You can:
+- Using root user (recommended): Using root user can avoid issues such as
permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for
start, stop and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute
commands with root privileges, which may cause confusion or security issues.
+
## Installation Steps
### 1、Unzip the installation package and enter the installation directory
@@ -95,6 +101,8 @@ Open the DataNode configuration file (./conf/iotdb-system.
properties file) and
| dn_schema_region_consensus_port | The port used by DataNode for metadata
replica consensus protocol communication | 10760 |
10760 | Cannot be modified after initial
startup |
| dn_seed_config_node | The ConfigNode address that the node
connects to when registering to join the cluster, i.e. cn_internal-address:
cn_internal_port | 127.0.0.1:10710 |
cn_internal_address:cn_internal_port | Cannot be modified after
initial startup |
+> ❗️Attention: Editors such as VSCode Remote do not have automatic
configuration saving function. Please ensure that the modified files are saved
persistently, otherwise the configuration items will not take effect
+
### 3、Start ConfigNode
Enter the sbin directory of iotdb and start confignode
diff --git
a/src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 6e4d7f8..9764bef 100644
---
a/src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -36,7 +36,13 @@ This chapter will introduce how to start an IoTDB standalone
instance, which inc
4. Whether in linux or windows, ensure that the IoTDB installation path does
not contain Spaces and Chinese characters to avoid software exceptions.
-5. It is recommended to deploy a monitoring panel, which can monitor important
operational indicators and keep track of database operation status at any time.
The monitoring panel can be obtained by contacting the business department, and
the steps for deploying the monitoring panel can be referred to：[Monitoring
Board Install and Deploy](./Monitoring-panel-deployment.md).
+5. Please note that when installing and deploying IoTDB (including activating
and using software), it is necessary to use the same user for operations. You
can:
+- Using root user (recommended): Using root user can avoid issues such as
permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for
start, activation, stop, and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute
commands with root privileges, which may cause confusion or security issues.
+
+6. It is recommended to deploy a monitoring panel, which can monitor important
operational indicators and keep track of database operation status at any time.
The monitoring panel can be obtained by contacting the business department, and
the steps for deploying the monitoring panel can be referred to：[Monitoring
Board Install and Deploy](./Monitoring-panel-deployment.md).
## Installation Steps
@@ -99,6 +105,8 @@ Open the DataNode configuration file (./conf/iotdb-system.
properties file) and
| dn_schema_region_consensus_port | The port used by DataNode for metadata
replica consensus protocol communication | 10760 | 10760
| Cannot be modified after initial
startup |
| dn_seed_config_node | The ConfigNode address that the node
connects to when registering to join the cluster, i.e. cn_internal-address:
cn_internal_port | 127.0.0.1:10710 | cn_internal_address:cn_internal_port
| Cannot be modified after initial startup |
+> ❗️Attention: Editors such as VSCode Remote do not have automatic
configuration saving function. Please ensure that the modified files are saved
persistently, otherwise the configuration items will not take effect
+
### 3、Start ConfigNode
Enter the sbin directory of iotdb and start confignode
@@ -169,4 +177,9 @@ When you see the display "Activated" on the far right, it
indicates successful a
-> The appearance of 'Activated (W)' indicates passive activation, indicating
that this Config Node does not have a license file (or has not issued the
latest license file with a timestamp). At this point, it is recommended to
check if the license file has been placed in the license folder. If not, please
place the license file. If a license file already exists, it may be due to
inconsistency between the license file of this node and the information of
other nodes. Please contact Timecho [...]
\ No newline at end of file
+> The appearance of 'Activated (W)' indicates passive activation, indicating
that this Config Node does not have a license file (or has not issued the
latest license file with a timestamp). At this point, it is recommended to
check if the license file has been placed in the license folder. If not, please
place the license file. If a license file already exists, it may be due to
inconsistency between the license file of this node and the information of
other nodes. Please contact Timecho [...]
+
+## Common Problem
+1. Multiple prompts indicating activation failure during deployment process
+ - Use the `ls -al` command: Use the `ls -al` command to check if the owner
information of the installation package root directory is the current user.
+ - Check activation directory: Check all files in the `./activation`
directory and whether the owner information is the current user.
\ No newline at end of file
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 74e2557..b3c5ee3 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -40,6 +40,12 @@ This section will take the IoTDB classic cluster deployment
architecture 3C3D (3
4. Whether in linux or windows, ensure that the IoTDB installation path does
not contain Spaces and Chinese characters to avoid software exceptions.
+5. Please note that when installing and deploying IoTDB, it is necessary to
use the same user for operations. You can:
+- Using root user (recommended): Using root user can avoid issues such as
permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for
start, stop and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute
commands with root privileges, which may cause confusion or security issues.
+
## Preparation Steps
1. Prepare the IoTDB database installation
package:：apache-iotdb-{version}-all-bin.zip（Please refer to the installation
package for
details：[IoTDB-Package](../Deployment-and-Maintenance/IoTDB-Package_apache.md)）
@@ -125,6 +131,8 @@ Open DataNode Configuration File
`./conf/iotdb-datanode.properties`,Set the foll
| dn_schema_region_consensus_port | The port used by DataNode for metadata
replica consensus protocol communication | 10760 | 10760
| 10760 | 10760 |
10760 | Cannot be modified after initial startup |
| dn_seed_config_node | The ConfigNode address that the node
connects to when registering to join the cluster, i.e. `cn_internal-address:
cn_internal_port` | 127.0.0.1:10710 | The first CongfigNode's
cn_internal-address: cn_internal_port | iotdb-1:10710 | iotdb-1:10710 |
iotdb-1:10710 | Cannot be modified after initial startup |
+> ❗️Attention: Editors such as VSCode Remote do not have automatic
configuration saving function. Please ensure that the modified files are saved
persistently, otherwise the configuration items will not take effect
+
### Start ConfigNode
Start the first confignode of IoTDB-1 first, ensuring that the seed confignode
node starts first, and then start the second and third confignode nodes in
sequence
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
index 99b92b9..0a75eb8 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
@@ -40,7 +40,13 @@ This section describes how to manually deploy an instance
that includes 3 Config
4. Whether in linux or windows, ensure that the IoTDB installation path does
not contain Spaces and Chinese characters to avoid software exceptions.
-5. It is recommended to deploy a monitoring panel, which can monitor important
operational indicators and keep track of database operation status at any time.
The monitoring panel can be obtained by contacting the business department,The
steps for deploying a monitoring panel can refer to:[Monitoring Panel
Deployment](./Monitoring-panel-deployment.md)
+5. Please note that when installing and deploying IoTDB (including activating
and using software), it is necessary to use the same user for operations. You
can:
+- Using root user (recommended): Using root user can avoid issues such as
permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for
start, activation, stop, and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute
commands with root privileges, which may cause confusion or security issues.
+
+6. It is recommended to deploy a monitoring panel, which can monitor important
operational indicators and keep track of database operation status at any time.
The monitoring panel can be obtained by contacting the business department,The
steps for deploying a monitoring panel can refer to:[Monitoring Panel
Deployment](./Monitoring-panel-deployment.md)
## Preparation Steps
@@ -126,6 +132,8 @@ Open DataNode Configuration File
`./conf/iotdb-datanode.properties`,Set the foll
| dn_schema_region_consensus_port | The port used by DataNode for metadata
replica consensus protocol communication | 10760 | 10760
| 10760 | 10760 |
10760 | Cannot be modified after initial startup |
| dn_seed_config_node | The ConfigNode address that the node
connects to when registering to join the cluster, i.e. `cn_internal-address:
cn_internal_port` | 127.0.0.1:10710 | The first CongfigNode's
cn_internal-address: cn_internal_port | iotdb-1:10710 | iotdb-1:10710 |
iotdb-1:10710 | Cannot be modified after initial startup |
+> ❗️Attention: Editors such as VSCode Remote do not have automatic
configuration saving function. Please ensure that the modified files are saved
persistently, otherwise the configuration items will not take effect
+
### Start ConfigNode
Start the first confignode of IoTDB-1 first, ensuring that the seed confignode
node starts first, and then start the second and third confignode nodes in
sequence
@@ -337,4 +345,9 @@ sbin/remove-datanode.sh [dn_rpc_address:dn_rpc_port]
#Windows
sbin/remove-datanode.bat [dn_rpc_address:dn_rpc_port]
-```
\ No newline at end of file
+```
+
+## Common Problem
+1. Multiple prompts indicating activation failure during deployment process
+ - Use the `ls -al` command: Use the `ls -al` command to check if the owner
information of the installation package root directory is the current user.
+ - Check activation directory: Check all files in the `./activation`
directory and whether the owner information is the current user.
\ No newline at end of file
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 62c3ac0..429233b 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
@@ -34,6 +34,12 @@
4. Whether in linux or windows, ensure that the IoTDB installation path does
not contain Spaces and Chinese characters to avoid software exceptions.
+5. Please note that when installing and deploying IoTDB, it is necessary to
use the same user for operations. You can:
+- Using root user (recommended): Using root user can avoid issues such as
permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for
start, stop and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute
commands with root privileges, which may cause confusion or security issues.
+
## Installation Steps
### Unzip the installation package and enter the installation directory
@@ -95,6 +101,8 @@ Open the DataNode configuration file
(./conf/iotdb-datanode.properties file) and
| dn_schema_region_consensus_port | The port used by DataNode for metadata
replica consensus protocol communication | 10760 |
10760 | Cannot be modified after initial
startup |
| dn_seed_config_node | The ConfigNode address that the node
connects to when registering to join the cluster, i.e. cn_internal-address:
cn_internal_port | 127.0.0.1:10710 |
cn_internal_address:cn_internal_port | Cannot be modified after
initial startup |
+> ❗️Attention: Editors such as VSCode Remote do not have automatic
configuration saving function. Please ensure that the modified files are saved
persistently, otherwise the configuration items will not take effect
+
### Start ConfigNode
Enter the sbin directory of iotdb and start confignode
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 905a7f4..cdf19f3 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -36,7 +36,13 @@ This chapter will introduce how to start an IoTDB standalone
instance, which inc
4. Whether in linux or windows, ensure that the IoTDB installation path does
not contain Spaces and Chinese characters to avoid software exceptions.
-5. It is recommended to deploy a monitoring panel, which can monitor important
operational indicators and keep track of database operation status at any time.
The monitoring panel can be obtained by contacting the business department, and
the steps for deploying the monitoring panel can be referred to：[Monitoring
Board Install and Deploy](./Monitoring-panel-deployment.md).
+5. Please note that when installing and deploying IoTDB (including activating
and using software), it is necessary to use the same user for operations. You
can:
+- Using root user (recommended): Using root user can avoid issues such as
permissions.
+- Using a fixed non root user:
+ - Using the same user operation: Ensure that the same user is used for
start, activation, stop, and other operations, and do not switch users.
+ - Avoid using sudo: Try to avoid using sudo commands as they execute
commands with root privileges, which may cause confusion or security issues.
+
+6. It is recommended to deploy a monitoring panel, which can monitor important
operational indicators and keep track of database operation status at any time.
The monitoring panel can be obtained by contacting the business department, and
the steps for deploying the monitoring panel can be referred to：[Monitoring
Board Install and Deploy](./Monitoring-panel-deployment.md).
## Installation Steps
@@ -99,6 +105,8 @@ Open the DataNode configuration file
(./conf/iotdb-datanode.properties file) and
| dn_schema_region_consensus_port | The port used by DataNode for metadata
replica consensus protocol communication | 10760 | 10760
| Cannot be modified after initial
startup |
| dn_seed_config_node | The ConfigNode address that the node
connects to when registering to join the cluster, i.e. cn_internal-address:
cn_internal_port | 127.0.0.1:10710 | cn_internal_address:cn_internal_port
| Cannot be modified after initial startup |
+> ❗️Attention: Editors such as VSCode Remote do not have automatic
configuration saving function. Please ensure that the modified files are saved
persistently, otherwise the configuration items will not take effect
+
### Start ConfigNode
Enter the sbin directory of iotdb and start confignode
@@ -168,4 +176,9 @@ When you see the display "Activated" on the far right, it
indicates successful a
-> The appearance of 'Activated (W)' indicates passive activation, indicating
that this Config Node does not have a license file (or has not issued the
latest license file with a timestamp). At this point, it is recommended to
check if the license file has been placed in the license folder. If not, please
place the license file. If a license file already exists, it may be due to
inconsistency between the license file of this node and the information of
other nodes. Please contact Timecho [...]
\ No newline at end of file
+> The appearance of 'Activated (W)' indicates passive activation, indicating
that this Config Node does not have a license file (or has not issued the
latest license file with a timestamp). At this point, it is recommended to
check if the license file has been placed in the license folder. If not, please
place the license file. If a license file already exists, it may be due to
inconsistency between the license file of this node and the information of
other nodes. Please contact Timecho [...]
+
+## Common Problem
+1. Multiple prompts indicating activation failure during deployment process
+ - Use the `ls -al` command: Use the `ls -al` command to check if the owner
information of the installation package root directory is the current user.
+ - Check activation directory: Check all files in the `./activation`
directory and whether the owner information is the current user.
\ No newline at end of file
diff --git
a/src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md
b/src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md
index 79a656b..7bbab16 100644
---
a/src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md
+++
b/src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md
@@ -40,6 +40,12 @@
4. 无论是在linux还是windows中，请确保IoTDB的安装路径中不含空格和中文，避免软件运行异常。
+5. 请注意，安装部署IoTDB时需要保持使用同一个用户进行操作，您可以：
+- 使用 root 用户（推荐）：使用 root 用户可以避免权限等问题。
+- 使用固定的非 root 用户：
+ - 使用同一用户操作：确保在启动、停止等操作均保持使用同一用户，不要切换用户。
+ - 避免使用 sudo：尽量避免使用 sudo 命令，因为它会以 root 用户权限执行命令，可能会引起权限混淆或安全问题。
+
## 准备步骤
1. 准备IoTDB数据库安装包
：apache-iotdb-{version}-all-bin.zip（安装包获取见：[链接](../Deployment-and-Maintenance/IoTDB-Package_apache.md)）
@@ -125,6 +131,8 @@ cd apache-iotdb-{version}-all-bin
| dn_schema_region_consensus_port | DataNode用于元数据副本共识协议通信使用的端口
| 10760 | 10760 |
10760 | 10760 | 10760 | 首次启动后不能修改 |
| dn_seed_config_node |
节点注册加入集群时连接的ConfigNode地址,即cn_internal_address:cn_internal_port |
127.0.0.1:10710 | 第一个CongfigNode的cn_internal_address:cn_internal_port |
iotdb-1:10710 | iotdb-1:10710 | iotdb-1:10710 | 首次启动后不能修改 |
+> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
+
### 启动ConfigNode节点
先启动第一个iotdb-1的confignode, 保证种子confignode节点先启动，然后依次启动第2和第3个confignode节点
diff --git
a/src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
b/src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
index 96d3cbf..b335295 100644
---
a/src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
+++
b/src/zh/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
@@ -40,7 +40,13 @@
4. 无论是在linux还是windows中，请确保IoTDB的安装路径中不含空格和中文，避免软件运行异常。
-5.
推荐部署监控面板，可以对重要运行指标进行监控，随时掌握数据库运行状态，监控面板可以联系商务获取，部署监控面板步骤可以参考：[监控面板部署](./Monitoring-panel-deployment.md)
+5. 请注意，安装部署（包括激活和使用软件）IoTDB时需要保持使用同一个用户进行操作，您可以：
+- 使用 root 用户（推荐）：使用 root 用户可以避免权限等问题。
+- 使用固定的非 root 用户：
+ - 使用同一用户操作：确保在启动、激活、停止等操作均保持使用同一用户，不要切换用户。
+ - 避免使用 sudo：尽量避免使用 sudo 命令，因为它会以 root 用户权限执行命令，可能会引起权限混淆或安全问题。
+
+6.
推荐部署监控面板，可以对重要运行指标进行监控，随时掌握数据库运行状态，监控面板可以联系商务获取，部署监控面板步骤可以参考：[监控面板部署](./Monitoring-panel-deployment.md)
## 准备步骤
@@ -126,6 +132,8 @@ cd iotdb-enterprise-{version}-bin
| dn_schema_region_consensus_port | DataNode用于元数据副本共识协议通信使用的端口
| 10760 | 10760 |
10760 | 10760 | 10760 | 首次启动后不能修改 |
| dn_seed_config_node |
节点注册加入集群时连接的ConfigNode地址,即cn_internal_address:cn_internal_port |
127.0.0.1:10710 | 第一个CongfigNode的cn_internal_address:cn_internal_port |
iotdb-1:10710 | iotdb-1:10710 | iotdb-1:10710 | 首次启动后不能修改 |
+> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
+
### 启动ConfigNode节点
先启动第一个iotdb-1的confignode, 保证种子confignode节点先启动，然后依次启动第2和第3个confignode节点
@@ -335,4 +343,10 @@ sbin/remove-datanode.sh [datanode_id]
#Windows
sbin/remove-datanode.bat [datanode_id]
-```
\ No newline at end of file
+```
+
+## 常见问题
+
+1. 部署过程中多次提示激活失败
+ - 使用 `ls -al` 命令：使用 `ls -al` 命令检查安装包根目录的所有者信息是否为当前用户。
+ - 检查激活目录：检查 `./activation` 目录下的所有文件，所有者信息是否为当前用户。
\ No newline at end of file
diff --git
a/src/zh/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
b/src/zh/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
index faff152..b7cbcb1 100644
---
a/src/zh/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
+++
b/src/zh/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -34,6 +34,12 @@
4. 无论是在linux还是windows中，请确保IoTDB的安装路径中不含空格和中文，避免软件运行异常。
+5. 请注意，安装部署IoTDB时需要保持使用同一个用户进行操作，您可以：
+- 使用 root 用户（推荐）：使用 root 用户可以避免权限等问题。
+- 使用固定的非 root 用户：
+ - 使用同一用户操作：确保在启动、停止等操作均保持使用同一用户，不要切换用户。
+ - 避免使用 sudo：尽量避免使用 sudo 命令，因为它会以 root 用户权限执行命令，可能会引起权限混淆或安全问题。
+
## 安装步骤
### 解压安装包并进入安装目录
@@ -95,6 +101,8 @@ cd apache-iotdb-{version}-all-bin
| dn_schema_region_consensus_port | DataNode用于元数据副本共识协议通信使用的端口
| 10760 | 10760 |
首次启动后不能修改 |
| dn_seed_config_node |
节点注册加入集群时连接的ConfigNode地址,即cn_internal_address:cn_internal_port |
127.0.0.1:10710 | cn_internal_address:cn_internal_port | 首次启动后不能修改 |
+> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
+
### 启动ConfigNode 节点
进入iotdb的sbin目录下，启动confignode
diff --git
a/src/zh/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/zh/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 6118221..fba9e24 100644
---
a/src/zh/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/zh/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -36,7 +36,13 @@
4. 无论是在linux还是windows中，请确保IoTDB的安装路径中不含空格和中文，避免软件运行异常。
-5.
推荐部署监控面板，可以对重要运行指标进行监控，随时掌握数据库运行状态，监控面板可以联系商务获取，部署监控面板步骤可以参考：[监控面板部署](./Monitoring-panel-deployment.md)。
+5. 请注意，安装部署（包括激活和使用软件）IoTDB时需要保持使用同一个用户进行操作，您可以：
+- 使用 root 用户（推荐）：使用 root 用户可以避免权限等问题。
+- 使用固定的非 root 用户：
+ - 使用同一用户操作：确保在启动、激活、停止等操作均保持使用同一用户，不要切换用户。
+ - 避免使用 sudo：尽量避免使用 sudo 命令，因为它会以 root 用户权限执行命令，可能会引起权限混淆或安全问题。
+
+6.
推荐部署监控面板，可以对重要运行指标进行监控，随时掌握数据库运行状态，监控面板可以联系商务获取，部署监控面板步骤可以参考：[监控面板部署](./Monitoring-panel-deployment.md)。
## 安装步骤
@@ -99,6 +105,8 @@ cd iotdb-enterprise-{version}-bin
| dn_schema_region_consensus_port | DataNode用于元数据副本共识协议通信使用的端口
| 10760 | 10760 |
首次启动后不能修改 |
| dn_seed_config_node |
节点注册加入集群时连接的ConfigNode地址,即cn_internal_address:cn_internal_port |
127.0.0.1:10710 | cn_internal_address:cn_internal_port | 首次启动后不能修改 |
+> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
+
### 启动 ConfigNode 节点
进入iotdb的sbin目录下，启动confignode
@@ -169,3 +177,10 @@ cd sbin
> 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件）。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请.
+
+
+## 常见问题
+
+1. 部署过程中多次提示激活失败
+ - 使用 `ls -al` 命令：使用 `ls -al` 命令检查安装包根目录的所有者信息是否为当前用户。
+ - 检查激活目录：检查 `./activation` 目录下的所有文件，所有者信息是否为当前用户。
\ No newline at end of file
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 935ad51..4568748 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
@@ -40,6 +40,12 @@
4. 无论是在linux还是windows中，请确保IoTDB的安装路径中不含空格和中文，避免软件运行异常。
+5. 请注意，安装部署IoTDB时需要保持使用同一个用户进行操作，您可以：
+- 使用 root 用户（推荐）：使用 root 用户可以避免权限等问题。
+- 使用固定的非 root 用户：
+ - 使用同一用户操作：确保在启动、停止等操作均保持使用同一用户，不要切换用户。
+ - 避免使用 sudo：尽量避免使用 sudo 命令，因为它会以 root 用户权限执行命令，可能会引起权限混淆或安全问题。
+
## 准备步骤
1. 准备IoTDB数据库安装包
：apache-iotdb-{version}-all-bin.zip（安装包获取见：[链接](../Deployment-and-Maintenance/IoTDB-Package_apache.md)）
@@ -125,6 +131,8 @@ cd apache-iotdb-{version}-all-bin
| dn_schema_region_consensus_port | DataNode用于元数据副本共识协议通信使用的端口
| 10760 | 10760 |
10760 | 10760 | 10760 | 首次启动后不能修改 |
| dn_seed_config_node |
节点注册加入集群时连接的ConfigNode地址,即cn_internal_address:cn_internal_port |
127.0.0.1:10710 | 第一个CongfigNode的cn_internal_address:cn_internal_port |
iotdb-1:10710 | iotdb-1:10710 | iotdb-1:10710 | 首次启动后不能修改 |
+> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
+
### 启动ConfigNode节点
先启动第一个iotdb-1的confignode, 保证种子confignode节点先启动，然后依次启动第2和第3个confignode节点
diff --git
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
index 2111aa0..069cc7f 100644
---
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
+++
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md
@@ -39,7 +39,13 @@
4. 无论是在linux还是windows中，请确保IoTDB的安装路径中不含空格和中文，避免软件运行异常。
-5.
推荐部署监控面板，可以对重要运行指标进行监控，随时掌握数据库运行状态，监控面板可以联系商务获取，部署监控面板步骤可以参考：[监控面板部署](./Monitoring-panel-deployment.md)
+5. 请注意，安装部署（包括激活和使用软件）IoTDB时需要保持使用同一个用户进行操作，您可以：
+- 使用 root 用户（推荐）：使用 root 用户可以避免权限等问题。
+- 使用固定的非 root 用户：
+ - 使用同一用户操作：确保在启动、激活、停止等操作均保持使用同一用户，不要切换用户。
+ - 避免使用 sudo：尽量避免使用 sudo 命令，因为它会以 root 用户权限执行命令，可能会引起权限混淆或安全问题。
+
+6.
推荐部署监控面板，可以对重要运行指标进行监控，随时掌握数据库运行状态，监控面板可以联系商务获取，部署监控面板步骤可以参考：[监控面板部署](./Monitoring-panel-deployment.md)
## 准备步骤
@@ -125,6 +131,8 @@ cd iotdb-enterprise-{version}-bin
| dn_schema_region_consensus_port | DataNode用于元数据副本共识协议通信使用的端口
| 10760 | 10760 |
10760 | 10760 | 10760 | 首次启动后不能修改 |
| dn_seed_config_node |
节点注册加入集群时连接的ConfigNode地址,即cn_internal_address:cn_internal_port |
127.0.0.1:10710 | 第一个CongfigNode的cn_internal_address:cn_internal_port |
iotdb-1:10710 | iotdb-1:10710 | iotdb-1:10710 | 首次启动后不能修改 |
+> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
+
### 启动ConfigNode节点
先启动第一个iotdb-1的confignode, 保证种子confignode节点先启动，然后依次启动第2和第3个confignode节点
@@ -335,4 +343,10 @@ sbin/remove-datanode.sh [dn_rpc_address:dn_rpc_port]
#Windows
sbin/remove-datanode.bat [dn_rpc_address:dn_rpc_port]
-```
\ No newline at end of file
+```
+
+## 常见问题
+
+1. 部署过程中多次提示激活失败
+ - 使用 `ls -al` 命令：使用 `ls -al` 命令检查安装包根目录的所有者信息是否为当前用户。
+ - 检查激活目录：检查 `./activation` 目录下的所有文件，所有者信息是否为当前用户。
\ No newline at end of file
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 b4b6c0b..5f005b2 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
@@ -34,6 +34,12 @@
4. 无论是在 linux 还是 windows 中，请确保 IoTDB 的安装路径中不含空格和中文，避免软件运行异常。
+5. 请注意，安装部署IoTDB时需要保持使用同一个用户进行操作，您可以：
+- 使用 root 用户（推荐）：使用 root 用户可以避免权限等问题。
+- 使用固定的非 root 用户：
+ - 使用同一用户操作：确保在启动、停止等操作均保持使用同一用户，不要切换用户。
+ - 避免使用 sudo：尽量避免使用 sudo 命令，因为它会以 root 用户权限执行命令，可能会引起权限混淆或安全问题。
+
## 安装步骤
### 解压安装包并进入安装目录
@@ -95,6 +101,8 @@ cd apache-iotdb-{version}-all-bin
| dn_schema_region_consensus_port | DataNode用于元数据副本共识协议通信使用的端口
| 10760 | 10760 |
首次启动后不能修改 |
| dn_seed_config_node |
节点注册加入集群时连接的ConfigNode地址,即cn_internal_address:cn_internal_port |
127.0.0.1:10710 | cn_internal_address:cn_internal_port | 首次启动后不能修改 |
+> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
+
### 启动ConfigNode 节点
进入iotdb的sbin目录下，启动confignode
diff --git
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
index 899ead5..5dfe0f8 100644
---
a/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
+++
b/src/zh/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md
@@ -36,7 +36,13 @@
4. 无论是在 linux 还是 windows 中，请确保 IoTDB 的安装路径中不含空格和中文，避免软件运行异常。
-5.
推荐部署监控面板，可以对重要运行指标进行监控，随时掌握数据库运行状态，监控面板可以联系商务获取，部署监控面板步骤可以参考：[监控面板部署](./Monitoring-panel-deployment.md)。
+5. 请注意，安装部署（包括激活和使用软件）IoTDB时需要保持使用同一个用户进行操作，您可以：
+- 使用 root 用户（推荐）：使用 root 用户可以避免权限等问题。
+- 使用固定的非 root 用户：
+ - 使用同一用户操作：确保在启动、激活、停止等操作均保持使用同一用户，不要切换用户。
+ - 避免使用 sudo：尽量避免使用 sudo 命令，因为它会以 root 用户权限执行命令，可能会引起权限混淆或安全问题。
+
+6.
推荐部署监控面板，可以对重要运行指标进行监控，随时掌握数据库运行状态，监控面板可以联系商务获取，部署监控面板步骤可以参考：[监控面板部署](./Monitoring-panel-deployment.md)。
## 安装步骤
@@ -99,6 +105,8 @@ cd iotdb-enterprise-{version}-bin
| dn_schema_region_consensus_port | DataNode用于元数据副本共识协议通信使用的端口
| 10760 | 10760 |
首次启动后不能修改 |
| dn_seed_config_node |
节点注册加入集群时连接的ConfigNode地址,即cn_internal_address:cn_internal_port |
127.0.0.1:10710 | cn_internal_address:cn_internal_port | 首次启动后不能修改 |
+> ❗️注意：VSCode Remote等编辑器无自动保存配置功能，请确保修改的文件被持久化保存，否则配置项无法生效
+
### 启动 ConfigNode 节点
进入iotdb的sbin目录下，启动confignode
@@ -169,3 +177,9 @@ cd sbin
> 出现`ACTIVATED(W)`为被动激活，表示此ConfigNode没有license文件（或没有签发时间戳最新的license文件）。此时建议检查license文件是否已放入license文件夹，没有请放入license文件，若已存在license文件，可能是此节点license文件与其他节点信息不一致导致，请联系天谋工作人员重新申请.
+
+## 常见问题
+
+1. 部署过程中多次提示激活失败
+ - 使用 `ls -al` 命令：使用 `ls -al` 命令检查安装包根目录的所有者信息是否为当前用户。
+ - 检查激活目录：检查 `./activation` 目录下的所有文件，所有者信息是否为当前用户。
\ No newline at end of file
