You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Bharat Viswanadham (Jira)" <ji...@apache.org> on 2020/12/08 18:25:00 UTC

[jira] [Resolved] (HDDS-3580) Retry Cache in OM

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

Bharat Viswanadham resolved HDDS-3580.
--------------------------------------
    Fix Version/s: 1.1.0
       Resolution: Fixed

> Retry Cache in OM
> -----------------
>
>                 Key: HDDS-3580
>                 URL: https://issues.apache.org/jira/browse/HDDS-3580
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: OM HA
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>             Fix For: 1.1.0
>
>         Attachments: Retry Cache in OM.pdf
>
>
> The failover proxy provider for OM HA retries requests on Network Timeout/Connectivity Exception. It can retry the request on the same OM or a new OM. If the request has been already processed, the subsequent retry will fail with error for non idempotent operations such as createVolume, createBucket createKey, renameKey etc. This will cause an application failure, unnecessary overhead in processing the operation again, and possibly corruption in metadata during failover.
> This Jira is to discuss this issue in detail,  and also categorize OM operations.



--
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