You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "Yongzao Dan (Jira)" <ji...@apache.org> on 2022/06/24 13:27:00 UTC

[jira] [Created] (IOTDB-3648) Reinforce ConfigNode startup process

Yongzao Dan created IOTDB-3648:
----------------------------------

             Summary: Reinforce ConfigNode startup process
                 Key: IOTDB-3648
                 URL: https://issues.apache.org/jira/browse/IOTDB-3648
             Project: Apache IoTDB
          Issue Type: Improvement
            Reporter: Yongzao Dan
            Assignee: Yongzao Dan
             Fix For: 0.14.0


The startup process of non-seed ConfigNode exists the following hidden dangers:
 # The register request should be send to ConfigNode-leader, but user can pick a random ConfigNode as register target. Therefore, we should add a retrying logic, and protect the redirecting logic.
 # The hidden parameter _configNodeList_ in ConfigNodeConfig is used in more than one place(ConfigNodeStartupCheck, ConsensusManager and NodeInfo) and can be confusing.
 # We should create a static class to manage all read/write opeartions involving the configNode-system.properties file



--
This message was sent by Atlassian Jira
(v8.20.7#820007)