Skip to content

[IOTDB-4206] Record DataNode's read-only status in ConfigNode#7108

Merged
qiaojialin merged 7 commits intoapache:masterfrom
CRZbulabula:Record_DataNode's_read-only_status
Aug 26, 2022
Merged

[IOTDB-4206] Record DataNode's read-only status in ConfigNode#7108
qiaojialin merged 7 commits intoapache:masterfrom
CRZbulabula:Record_DataNode's_read-only_status

Conversation

@CRZbulabula
Copy link
Contributor

@CRZbulabula CRZbulabula commented Aug 24, 2022

The DataNode has status ReadOnly which indicates itself has persistence problem. It's the duty of ConfigNode-leader to monitor DataNodes' running status and take corrective measures when some DataNodes run abnormally. The ConfigNode-leader will have the ability to monitor DataNode's ReadOnly and Error status after the following updates:

  1. Merge SystemStatus into NodeStatus
  2. DataNodes will report their status during each heartbeat
  3. ConfigNode-leader will broadcast the latest RegionRouteMap as soon as some DataNodes change their status.

Copy link
Member

@Beyyes Beyyes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change the variable naming of NodeStatus to CAPITAL and UNDERLINE when next pr.

Copy link
Contributor

@HeimingZ HeimingZ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

@qiaojialin qiaojialin merged commit 37d6cfe into apache:master Aug 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants