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/12/31 12:34:00 UTC

[jira] [Resolved] (RATIS-1636) Support re-config ratis properties

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

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

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

> Support re-config ratis properties
> ----------------------------------
>
>                 Key: RATIS-1636
>                 URL: https://issues.apache.org/jira/browse/RATIS-1636
>             Project: Ratis
>          Issue Type: New Feature
>          Components: server, shell
>            Reporter: Yaolong Liu
>            Assignee: Yaolong Liu
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: 800_review.patch
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> 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)