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

Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/10/26 20:04:00 UTC

[jira] [Updated] (HDDS-5872) Do not failover on some RpcExceptions

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

ASF GitHub Bot updated HDDS-5872:
---------------------------------
    Labels: pull-request-available  (was: )

> Do not failover on some RpcExceptions
> -------------------------------------
>
>                 Key: HDDS-5872
>                 URL: https://issues.apache.org/jira/browse/HDDS-5872
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>              Labels: pull-request-available
>
> When OMFailoverProxy encounters an RpcException, we should check if a failover or retry is required or not.
> For example, if the response length exceeds ipc.maximum.response.length on one OM, it will exceed the limit on all OMs. So we do not need to do a retry or failover.
> If there is an RpcNoSuchMethodException, RpcNoSuchProtocolException or VersionMismatch Exception etc. on only 1 OM and not of others, it could lead to state divergence between the OMs. So it would be better to fail the request than to retry on other nodes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org