[GitHub] [iotdb] CRZbulabula commented on pull request #7345: [IOTDB-4419] Maintain RegionStatus through cluster heartbeat

[GitBox <gi...@apache.org>]

CRZbulabula commented on PR #7345:
URL: https://github.com/apache/iotdb/pull/7345#issuecomment-1249386104

   > If RegionStatus also shown as `Unkonwn` when datanode is `ReadOnly` or `Removing`? Do we need adding `ReadOnly` or `Removing` status for RegionStatus later?
   
   I've thought these two cases:
   
   1. For DataNode in 'ReadOnly' status: It doesn't mean that the Region is in 'ReadOnly' status if the DataNode where the Region situated is currently 'ReadOnly'. Actually, we havn't defined in which scenario a Region is 'ReadOnly'. On the other hand, the ConfigNode-leader will consider a RegionGroup is 'Disabled' if one of its Region's located DataNode is 'ReadOnly'.
   2. For DataNode in 'Removing' status: It might be better to set the corresponding Regions into 'Removing' status either?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org