[jira] [Updated] (HDDS-2967) Add Transaction Log Index to OM Audit Logs

["Arpit Agarwal (Jira)" <ji...@apache.org>]

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

Arpit Agarwal updated HDDS-2967:
--------------------------------
    Target Version/s: 0.6.0  (was: 0.5.0)
              Labels: TriagePending  (was: )

> Add Transaction Log Index to OM Audit Logs
> ------------------------------------------
>
>                 Key: HDDS-2967
>                 URL: https://issues.apache.org/jira/browse/HDDS-2967
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Hanisha Koneru
>            Priority: Major
>              Labels: TriagePending
>
> When ratis is enabled for OM, it is possible that transactions will be replayed. Though most of the replays would be caught and ignored, there are some scenarios in which a transaction could be replayed.
> For example, Key1 is created and deleted. If Key1 create transaction is replayed, there is no way to determine if this is replayed transaction as Key1 would not be existing in the DB anymore. Replaying this transaction would be ok as the delete Key1 transaction would also be replayed.
> Though in such scenarios replaying transactions is ok, the audit log would also have a duplicate entry corresponding to the replayed transaction. To distinguish duplicate transactions, we propose adding the transactionLogIndex to the audit log for OM operations.



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