[ 
https://issues.apache.org/jira/browse/IOTDB-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yongzao Dan reopened IOTDB-6119:
--------------------------------

This issue should be resolved by adding the following interfaces to 
ConfigNode's consensus layer:

 
 # notifyLeaderReady: The consensus layer invoke this interface after a log 
that corresponding the current leader term is replied.
 # isLeaderReady: This interface should replace the current isLeader check. The 
new interface wouldn't return true until a log that corresponding the current 
leader term is replied.

> Add ConfigNode leader service check
> -----------------------------------
>
>                 Key: IOTDB-6119
>                 URL: https://issues.apache.org/jira/browse/IOTDB-6119
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: Yongzao Dan
>            Assignee: Yongzao Dan
>            Priority: Major
>              Labels: pull-request-available
>
> The ConfigNode-leader can't provide services until all of its leader services 
> are ready. Therefore there should add another AtomicBoolean to mark the 
> leader services' status.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to