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

Posted to issues@ratis.apache.org by "Song Ziyang (Jira)" <ji...@apache.org> on 2022/08/12 02:22:00 UTC

[jira] [Commented] (RATIS-1670) Timeout directly during startup

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

Song Ziyang commented on RATIS-1670:
------------------------------------

 [~szetszwo] What do you think?

 

> Timeout directly during startup
> -------------------------------
>
>                 Key: RATIS-1670
>                 URL: https://issues.apache.org/jira/browse/RATIS-1670
>             Project: Ratis
>          Issue Type: Improvement
>            Reporter: Song Ziyang
>            Priority: Major
>             Fix For: 2.4.0
>
>
> ElectionTimeout determines the average waiting time when a new RaftGroup initially startup. In practice, IoTDB sets ElectionTimeout = (6s-12s) to reduce elections cause by leader GC or other time-consuming activities. However, this means a newly started raft group usually has to wait for about 10s before its first successful write, which is annoying.
> It is possible for RaftGroup to timeout immediately when initially starts up. Or can we manually timeout a member?



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