[
https://issues.apache.org/jira/browse/HDDS-17320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-17320:
------------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> SCM client does not recognize RetriableWithNoFailoverException returned by SCM
> ------------------------------------------------------------------------------
>
> Key: HDDS-17320
> URL: https://issues.apache.org/jira/browse/HDDS-17320
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM Client
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> SCM converts errors that should be retried on the same SCM (Ratis
> {{LeaderNotReadyException}}, {{ReconfigurationInProgressException}},
> {{ReconfigurationTimeoutException}}, {{ResourceUnavailableException}}, and
> some certificate failures) to {{RetriableWithNoFailoverException}}
> (HDDS-5050). The SCM client checks for it with
> {{SCMHAUtils.checkRetriableWithNoFailoverException}}, which looks at the
> exception unwrapped from {{RemoteException}}. But
> {{RetriableWithNoFailoverException}} has no {{String}} constructor, so
> {{RemoteException.unwrapRemoteException()}} cannot create it and returns the
> {{RemoteException}} itself. The check never matches, so the client fails over
> to another SCM instead of retrying the same one.
> Proposed fix: add a {{String}} constructor to
> {{RetriableWithNoFailoverException}}, as HDDS-10760 did for other exceptions,
> so it can be unwrapped from {{RemoteException}}.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
