[
https://issues.apache.org/jira/browse/HDDS-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Shao Hong updated HDDS-5686:
-------------------------------
Description:
Background:
In a raft based ha cluster, for some reason, we want to transfer leadership to
a specific follower gracefully, now, we have to kill the leader master to
transfer leadership, but the leadership could transfer to a unexpected
follower, we have to kill the leader master again,this is so tricky.
Usage:
This feature is assumed to utilizing a shell command like ```ozone admin
failover -domain [SCM/OM] -address [IpAddr] ```, with optional IpAddr we can
transfer the leadership to the target follower.
Scenarios:
* We need to test every ratis node if each of them could be capable of being
the leader.
* During replacing ratis nodes for some reason, we need to stabilize the
process of changing the leadership, instead of forcely shuting down some node
Impl:
The alluxio community has already implemented this feature, we could backport
from them. They leverage the ratis support of setting priority for each member
among the raft group which insures the highest priority node could become a
leader.
was:
Background:
In a raft based ha cluster, for some reason, we want to transfer leadership to
a specific follower gracefully, now, we have to kill the leader master to
transfer leadership, but the leadership could transfer to a unexpected
follower, we have to kill the leader master again,this is so tricky.
Usage:
This feature is assumed to utilizing a shell command like ```ozone admin scm
failover [IpAddr] ```, with optional IpAddr we can transfer the leadership to
the target follower.
Scenarios:
* We need to test every ratis node if each of them could be capable of being
the leader.
* During replacing ratis nodes for some reason, we need to stabilize the
process of changing the leadership, instead of forcely shuting down some node
Impl:
The alluxio community has already implemented this feature, we could backport
from them. They leverage the ratis support of setting priority for each member
among the raft group which insures the highest priority node could become a
leader.
> Support transfer leadership to a specific follower master in raft based ha
> cluster
> ----------------------------------------------------------------------------------
>
> Key: HDDS-5686
> URL: https://issues.apache.org/jira/browse/HDDS-5686
> Project: Apache Ozone
> Issue Type: New Feature
> Reporter: Xu Shao Hong
> Assignee: Xu Shao Hong
> Priority: Minor
>
> Background:
> In a raft based ha cluster, for some reason, we want to transfer leadership
> to a specific follower gracefully, now, we have to kill the leader master to
> transfer leadership, but the leadership could transfer to a unexpected
> follower, we have to kill the leader master again,this is so tricky.
>
> Usage:
> This feature is assumed to utilizing a shell command like ```ozone admin
> failover -domain [SCM/OM] -address [IpAddr] ```, with optional IpAddr we
> can transfer the leadership to the target follower.
>
> Scenarios:
> * We need to test every ratis node if each of them could be capable of being
> the leader.
> * During replacing ratis nodes for some reason, we need to stabilize the
> process of changing the leadership, instead of forcely shuting down some node
>
> Impl:
> The alluxio community has already implemented this feature, we could backport
> from them. They leverage the ratis support of setting priority for each
> member among the raft group which insures the highest priority node could
> become a leader.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
