Skip to content

[IOTDB-4497] Improve NodeStatus definition #9256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OneSizeFitsQuorum merged 2 commits into from
Mar 9, 2023
Merged

[IOTDB-4497] Improve NodeStatus definition #9256

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
70ff1c3
Finish
CRZbulabula Mar 9, 2023
90b1297
create schema
CRZbulabula Mar 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions docs/UserGuide/Cluster/Cluster-Maintenance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,8 +136,19 @@ The DataNode statuses are defined as follows:
- The cluster is still readable and writable if some DataNodes are Removing
- **ReadOnly**: The remaining disk space of DataNode is lower than disk_warning_threshold(default is 5%), the DataNode is readable but un-writable and cannot synchronize data.
- The cluster is still readable and writable if some DataNodes are ReadOnly
- Schema, data and Database can be deleted in ReadOnly status
- Schema and data cannot be written to the cluster when all DataNodes are ReadOnly, but new Databases can still be created
- The schema and data in a ReadOnly DataNode is readable
- The schema and data in a ReadOnly DataNode is deletable
- A ReadOnly DataNode is creatable for schema, but un-writable for data
- Data cannot be written to the cluster when all DataNodes are ReadOnly, but new Databases and schema is still creatable

**For a DataNode**, the following table describes the impact of schema read, write, and deletion in different status:

| DataNode status | readable | creatable | deletable |
|-----------------|----------|-----------|-----------|
| Running | yes | yes | yes |
| Unknown | no | no | no |
| Removing | no | no | no |
| ReadOnly | yes | yes | yes |

**For a DataNode**, the following table describes the impact of data read, write, and deletion in different status:

Expand Down
21 changes: 16 additions & 5 deletions docs/zh/UserGuide/Cluster/Cluster-Maintenance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,13 +132,24 @@ DataNode 的状态机如下图所示：

- **Running**: DataNode 正常运行，可读可写
- **Unknown**: DataNode 未正常上报心跳，ConfigNode 认为该 DataNode 不可读写
- 少数 DataNode Unknown 不影响集群读写
- 少数 Unknown DataNode 不影响集群读写
- **Removing**: DataNode 正在移出集群，不可读写
- 少数 DataNode Removing 不影响集群读写
- 少数 Removing DataNode 不影响集群读写
- **ReadOnly**: DataNode 磁盘剩余空间低于 disk_warning_threshold（默认 5%），DataNode 可读但不能写入，不能同步数据
- 少数 DataNode ReadOnly 不影响集群读写
- ReadOnly 状态下可以删除元数据和数据，可以删除 Database
- 所有 DataNode 处于 ReadOnly 状态时，集群不可写入元数据和数据，仍可以创建 Database
- 少数 ReadOnly DataNode 不影响集群读写
- ReadOnly DataNode 可以查询元数据和数据
- ReadOnly DataNode 可以删除元数据和数据
- ReadOnly DataNode 可以创建元数据，不能写入数据
- 所有 DataNode 处于 ReadOnly 状态时，集群不能写入数据，仍可以创建 Database 和元数据

**对于一个 DataNode**，不同状态元数据查询、创建、删除的影响如下表所示：

| DataNode 状态 | 可读 | 可创建 | 可删除 |
|-------------|-----|-----|-----|
| Running | 是 | 是 | 是 |
| Unknown | 否 | 否 | 否 |
| Removing | 否 | 否 | 否 |
| ReadOnly | 是 | 是 | 是 |

**对于一个 DataNode**，不同状态数据查询、写入、删除的影响如下表所示：

Expand Down