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/07/22 16:37:00 UTC

[jira] [Commented] (RATIS-1636) Support lock leadership on the specific server

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

Tsz-wo Sze commented on RATIS-1636:
-----------------------------------

bq. ... I found that if the program stops at the breakpoint for a period of time, the leader will switch to another server, ...

This is the timeout specified in the Raft algorithm.

bq. ... Can we add a feature to lock the leader on the specific server?

How would it work?

> Support lock leadership on the specific server
> ----------------------------------------------
>
>                 Key: RATIS-1636
>                 URL: https://issues.apache.org/jira/browse/RATIS-1636
>             Project: Ratis
>          Issue Type: New Feature
>          Components: server, shell
>            Reporter: Yaolong Liu
>            Priority: Major
>
> Recently, when I was debugging code, I found that if the program stops at the breakpoint for a period of time, the leader will switch to another server, which is not conducive to my troubleshooting. Can we add a feature to lock the leader on the specific server?



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