[
https://issues.apache.org/jira/browse/RATIS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175804#comment-17175804
]
Tsz-wo Sze commented on RATIS-967:
----------------------------------
> ... it's priority is less than s2's, but s2's log is lag behind than s1.
> Then it will cause no leader can be elected.
That's a good point. How about when s2 receives the vote request from s1, it
will compare the log. If s2's log is lag behind, then s2 will vote for s1 even
s2 has a higher priority.
When a higher priority server joins an existing group but its log is lagging
behind. The existing leader won't yield the leadership yet. It will first
allow the higher priority server to catch up and then yield the leadership.
Indeed, the logic is first comparing the log and then the priority.
> Transfer leadership from leader to follower
> -------------------------------------------
>
> Key: RATIS-967
> URL: https://issues.apache.org/jira/browse/RATIS-967
> Project: Ratis
> Issue Type: Sub-task
> Components: raft-group
> Affects Versions: 0.5.0
> Reporter: maobaolong
> Assignee: runzhiwang
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> With this api, we can transition leader state to a specify one for datanodes
> in the same pipeline, OM group and SCM group.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
