You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Hanisha Koneru (Jira)" <ji...@apache.org> on 2019/12/17 01:41:00 UTC
[jira] [Created] (HDDS-2755) Compare transactionID and updateID of
Volume operations to avoid replaying transactions
Hanisha Koneru created HDDS-2755:
------------------------------------
Summary: Compare transactionID and updateID of Volume operations to avoid replaying transactions
Key: HDDS-2755
URL: https://issues.apache.org/jira/browse/HDDS-2755
Project: Hadoop Distributed Data Store
Issue Type: Sub-task
Components: om
Reporter: Hanisha Koneru
Assignee: Hanisha Koneru
To ensure that volume operations are idempotent, we should first 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.
--
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