You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2022/08/19 15:20:00 UTC

[jira] [Resolved] (RATIS-1638) Ignore the first timeout and initiate an election directly

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

Tsz-wo Sze resolved RATIS-1638.
-------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

The pull request is now merged.  Thanks, [~William Song]!

> Ignore the first timeout and initiate an election directly
> ----------------------------------------------------------
>
>                 Key: RATIS-1638
>                 URL: https://issues.apache.org/jira/browse/RATIS-1638
>             Project: Ratis
>          Issue Type: New Feature
>            Reporter: Yaolong Liu
>            Assignee: Song Ziyang
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> We use Alluxio to call Ratis's service, and found that if the election expiration time is set too small, leader switching is easy to occur when full gc occurs, but if the election expiration time is set longer, then when the service is started for the first time It takes a long time to initiate an election. This waiting time is not what we want to see. Can we complete a feature to make the timeout for the first startup shorter, which can reduce the service unavailability time. 



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