[ https://issues.apache.org/jira/browse/IOTDB-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
LiYuheng reassigned IOTDB-6129: ------------------------------- Assignee: LiYuheng > ConfigNode restarts without relying on Seed-ConfigNode > ------------------------------------------------------ > > Key: IOTDB-6129 > URL: https://issues.apache.org/jira/browse/IOTDB-6129 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Cluster > Reporter: LiYuheng > Assignee: LiYuheng > Priority: Major > > [https://apache-iotdb.feishu.cn/docs/doccnSfXXrSbLu3ETmDWLY5tmwu#H8SOcB] > [https://github.com/apache/iotdb/pull/10988] > > As of version 1.2.1, the roles of the current ConfigNode are divided into > Seed-ConfigNode and non-Seed-ConfigNode. The former is the first started > ConfigNode, and the latter is the ConfigNode started later. > After forming a multi-replica ConfigNode cluster, a Leader-ConfigNode and > several Follower-ConfigNodes are selected. The expected behavior is that when > a small number of ConfigNode nodes go down, the ConfigNode cluster can still > elect a Leader and provide services to meet high availability requirements. > However, in the current implementation, the non-Seed-ConfigNode depends on > the Seed-ConfigNode during restart. That is, if the Seed-ConfigNode goes > down, other non-Seed-ConfigNodes cannot restart, which poses a risk to the > high availability guarantee of the IoTDB ConfigNode cluster. > Therefore, it is expected in version 1.2.2 to remove the dependency of > non-Seed-ConfigNode on Seed-ConfigNode during restart, further enhancing the > high availability of IoTDB ConfigNode. -- This message was sent by Atlassian Jira (v8.20.10#820010)