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/07/08 03:17:00 UTC

[jira] [Commented] (IOTDB-3779) The Non-Seed-ConfigNode should suicide if waiting leader's scheduling for too long

    [ https://issues.apache.org/jira/browse/IOTDB-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564064#comment-17564064 ] 

Yongzao Dan commented on IOTDB-3779:
------------------------------------

Blocked by https://issues.apache.org/jira/browse/IOTDB-3780 

> The Non-Seed-ConfigNode should suicide if waiting leader's scheduling for too long
> ----------------------------------------------------------------------------------
>
>                 Key: IOTDB-3779
>                 URL: https://issues.apache.org/jira/browse/IOTDB-3779
>             Project: Apache IoTDB
>          Issue Type: New Feature
>            Reporter: Yongzao Dan
>            Assignee: Yongzao Dan
>            Priority: Major
>             Fix For: 0.14.0
>
>
> It's obviously that this new feature is necessary. I decide to complete this feature by judging if the current Non-Seed-ConfigNode joins in the ConsensusGroup sucessfully.



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