[
https://issues.apache.org/jira/browse/HDDS-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4230:
----------------------------
Description:
It is an enhancement for HDDS-3188.
Like OMFailoverProxyProvider, SCMBlockLocationFailoverProxyProvider should also
handle LeaderNotReadyException.
If SCM client (like OzoneManager) has touched leader SCM, meanwhile leader SCM
is stuck in replaying raft log entries(e.g., that SCM restarts and becomes
leader, it needs time to recover its state machine by replaying all raft log
entries), SCM client should not round robin to the next SCM, It should wait and
retry the same SCM later.
was:
like OMFailoverProxyProvider, SCMBlockLocationFailoverProxyProvider should
also handle LeaderNotReadyException.
If scm client (like OzoneManager) has touched leader SCM, meanwhile leader SCM
is stuck in replaying raft log entries, scm client should not round robin to
next SCM, It should wait and retry the same SCM later.
> SCMBlockLocationFailoverProxyProvider should handle LeaderNotReadyException
> ---------------------------------------------------------------------------
>
> Key: HDDS-4230
> URL: https://issues.apache.org/jira/browse/HDDS-4230
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: SCM
> Reporter: Glen Geng
> Assignee: Li Cheng
> Priority: Major
> Labels: pull-request-available
>
> It is an enhancement for HDDS-3188.
> Like OMFailoverProxyProvider, SCMBlockLocationFailoverProxyProvider should
> also handle LeaderNotReadyException.
> If SCM client (like OzoneManager) has touched leader SCM, meanwhile leader
> SCM is stuck in replaying raft log entries(e.g., that SCM restarts and
> becomes leader, it needs time to recover its state machine by replaying all
> raft log entries), SCM client should not round robin to the next SCM, It
> should wait and retry the same SCM later.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
