You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Glen Geng (Jira)" <ji...@apache.org> on 2020/09/10 11:21:01 UTC

[jira] [Assigned] (HDDS-4230) SCMBlockLocationFailoverProxyProvider should handle LeaderNotReadyException

     [ https://issues.apache.org/jira/browse/HDDS-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Glen Geng reassigned HDDS-4230:
-------------------------------

    Assignee:     (was: Li Cheng)

> 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
>            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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org