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

Ivan Andika updated HDDS-9627:
------------------------------
    Description: 
Currently, Ratis transfer leadership uses priority as a way for the previous 
leader to yield its leadership to the target peer with higher priority.

The implementation in Ozone uses setConfiguration API to set the target peer's 
priority to 2 while the rest is set to 1.

However, we need to reset the priorities to 1 after transfer leadership 
(regardless of the transfer leadership result) to avoid cases where the same 
Raft peer will always be favored to be the leader (even if the peer is slow).

Note: 

  was:
Currently, Ratis transfer leadership uses priority as a way for the previous 
leader to yield its leadership to the target peer with higher priority.

The implementation in Ozone uses setConfiguration API to set the target peer's 
priority to 2 while the rest is set to 1.

However, we need to reset the priorities to 1 after transfer leadership 
(regardless of the transfer leadership result) to avoid cases where the same 
Raft peer will always be favored to be the leader (even if the peer is slow).


> Reset RaftPeer priorities after transfer leadership
> ---------------------------------------------------
>
>                 Key: HDDS-9627
>                 URL: https://issues.apache.org/jira/browse/HDDS-9627
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ivan Andika
>            Assignee: Ivan Andika
>            Priority: Major
>
> Currently, Ratis transfer leadership uses priority as a way for the previous 
> leader to yield its leadership to the target peer with higher priority.
> The implementation in Ozone uses setConfiguration API to set the target 
> peer's priority to 2 while the rest is set to 1.
> However, we need to reset the priorities to 1 after transfer leadership 
> (regardless of the transfer leadership result) to avoid cases where the same 
> Raft peer will always be favored to be the leader (even if the peer is slow).
> Note: 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to