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/01/31 23:05:00 UTC

[jira] [Resolved] (HDDS-2956) Handle Replay of AllocateBlock request

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

Bharat Viswanadham resolved HDDS-2956.
--------------------------------------
    Fix Version/s: 0.5.0
       Resolution: Fixed

> Handle Replay of AllocateBlock request
> --------------------------------------
>
>                 Key: HDDS-2956
>                 URL: https://issues.apache.org/jira/browse/HDDS-2956
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> To ensure that allocate block operations are idempotent, compare the transactionID with the objectID and updateID to make sure that the transaction is not a replay. If the transactionID <= updateID, then it implies that the transaction is a replay and hence it should be skipped.
> OMAllocateBlockRequest is made idempotent in this Jira.



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

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