[
https://issues.apache.org/jira/browse/HDDS-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133435#comment-18133435
]
Ivan Andika commented on HDDS-4230:
-----------------------------------
I will address both LeaderNotReadyException and LeaderSteppingDownException in
HDDS-16028
> SCMBlockLocationFailoverProxyProvider should handle LeaderNotReadyException
> ---------------------------------------------------------------------------
>
> Key: HDDS-4230
> URL: https://issues.apache.org/jira/browse/HDDS-4230
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Glen Geng
> Assignee: Rui Wang
> Priority: Major
>
> 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
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
