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

["Yaolong Liu (Jira)" <ji...@apache.org>]

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

Yaolong Liu edited comment on RATIS-1636 at 7/23/22 3:40 PM:
-------------------------------------------------------------

[~szetszwo] Thanks for reply.
Yes, once the debug time exceeds the timeout , the cluster will switch leader. My assumption is whether we can support dynamic update the property of timeout and then when debugging. We can execute a command similar to 
{code:bash}
bin/ratis sh property-set xxx.xxx.timeout=xxx
{code}
so is this feature completed to a certain extent?  Or, do you have any good suggestions?


was (Author: JIRAUSER280039):
[~szetszwo] Thanks for reply.
Yes, once the debug time exceeds the timeout , the cluster will switch leader. My assumption is whether we can support dynamic update the property of timeout and then when debugging. We can execute a command similar to 
{code:shell}
bin/ratis sh property-set xxx.xxx.timeout=xxx
{code}
so is this feature completed to a certain extent?  Or, do you have any good suggestions?

> 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)