You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Hui Fei (Jira)" <ji...@apache.org> on 2026/06/09 04:28:05 UTC
[jira] [Updated] (HDDS-3325) Handle Resource Unavailable exception in OM HA
[ https://issues.apache.org/jira/browse/HDDS-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hui Fei updated HDDS-3325:
--------------------------
Target Version/s: 2.3.0 (was: 2.2.0)
<<Bulk update>>
Apache Ozone 2.2.0 release is in progress. I'm updating all unresolved jiras targeting 2.2.0 to retarget 2.3.0.
> Handle Resource Unavailable exception in OM HA
> ----------------------------------------------
>
> Key: HDDS-3325
> URL: https://issues.apache.org/jira/browse/HDDS-3325
> Project: Apache Ozone
> Issue Type: Bug
> Components: OM HA, Ozone Manager
> Reporter: Bharat Viswanadham
> Assignee: Ritesh Shukla
> Priority: Major
> Labels: TriagePending
>
> Right now, when the future fails with an exception, we send that exception to the client, and retry with a new server. but when using ratis server when resource unavailable exception future fails with exceptionally. So, in this case we need to wrap the exception and retry to the same server with some retry policy like MultiLinearRandomRetry or some retry policy.
> {code:java}
> try {
> raftClientReply = server.submitClientRequestAsync(raftClientRequest)
> .get();
> } catch (Exception ex) {
> throw new ServiceException(ex.getMessage(), ex);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org