[HDDS-9627] Reset RaftPeer priorities after transfer leadership

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 1.4.0
• Labels: pull-request-available
• Assignee: Ivan Andika
• Reporter: Ivan Andika
• Created: 03/Nov/23 09:24
• Updated: 12/Nov/23 15:41
• Resolved: 12/Nov/23 15:31

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

There is also a new way to transfer leadership logic without changing priorities, this can be done in a separate task.

Issue Links

• links to: GitHub Pull Request #5549