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

Song Ziyang resolved RATIS-1930.
--------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

The PR is now merged. Thanks [~szetszwo] for working on this!

> Add a conf for enable/disable majority-add.
> -------------------------------------------
>
>                 Key: RATIS-1930
>                 URL: https://issues.apache.org/jira/browse/RATIS-1930
>             Project: Ratis
>          Issue Type: Improvement
>          Components: server
>            Reporter: Tsz-wo Sze
>            Assignee: Tsz-wo Sze
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> RATIS-1912 added a restriction on setConf for enforcing a safety property, 
> otherwise, the server group may end up in a no-leader state and cannot 
> recover by themselves. The restriction is to disallow majority-add as defined 
> below
>  - {*}Majority-add{*}: adding a majority of server in a single setConf.  Note 
> that, when a single setConf removes and adds members at the same time, the 
> majority is counted after the removal.
> This JIRA is to add a conf for enable/disable majority-add since, in some 
> monitored environment, the safety property is not a problem. The monitor (a 
> human or a program) could intervene to fix the problem, if it happens. 
> Disabling the restriction can improve performance. For example, change from 
> non-HA single server to a HA 3-server group can be done in a single setConf, 
> instead of 2 setConfs with the restriction.



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

Reply via email to