You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Bharat Viswanadham (Jira)" <ji...@apache.org> on 2020/11/19 00:46:00 UTC
[jira] [Created] (HDDS-4484) Use RatisServerImpl isLeader instead
of periodic leader update logic in OM
Bharat Viswanadham created HDDS-4484:
----------------------------------------
Summary: Use RatisServerImpl isLeader instead of periodic leader update logic in OM
Key: HDDS-4484
URL: https://issues.apache.org/jira/browse/HDDS-4484
Project: Hadoop Distributed Data Store
Issue Type: Bug
Reporter: Bharat Viswanadham
Assignee: Bharat Viswanadham
Previously RatisServer which is network-partitoned/split-brain does not step down from leader state, so we require custom logic to determine leader(But that is also not completely correct, as the role state is updated based on server state not a quorum based information)
Now, in Ratis leader steps down after the leader election max time out, so we can use RaftServer Api isLeader check. (RATIS-981 fixed this behavior)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org