[
https://issues.apache.org/jira/browse/HDDS-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Pogde updated HDDS-2967:
---------------------------------
Target Version/s: 1.2.0
I am managing the 1.1.0 release and we currently have more than 600 issues
targeted for 1.1.0. I am moving the target field to 1.2.0.
If you are actively working on this jira and believe this should be targeted to
1.1.0 release, Please change the target field back to 1.1.0 before Feb 05,
2021.
> 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
> Components: OM HA, Ozone Manager
> Reporter: Hanisha Koneru
> Assignee: Dinesh Chitlangia
> 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: [email protected]
For additional commands, e-mail: [email protected]
