[
https://issues.apache.org/jira/browse/HDDS-10948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850870#comment-17850870
]
Ethan Rose commented on HDDS-10948:
-----------------------------------
Possible duplicate of HDDS-10658?
> log transaction Id for every operation including exception causing termination
> ------------------------------------------------------------------------------
>
> Key: HDDS-10948
> URL: https://issues.apache.org/jira/browse/HDDS-10948
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Manager
> Reporter: Sumit Agrawal
> Assignee: Sumit Agrawal
> Priority: Minor
>
> As part of HDDS-9342 where transaction replay was causing OM startup failure,
> and to recover same, need update transaction ID to one already applied.
> Similarly, if any code bug in feature causes OM crash while apply
> Transaction. To recover this situation based on impact, need update
> Transaction Id in transactionInfo table of OM rocks db.
> To identify transaction Id which needs to be updated, this is difficult from
> db and ratis log. Audit log can provide the information about transaction
> applied, with transaction ID.
>
> So as part of this,
> * Need add transactionId for existing audit log
> * For Exceptional scenario, need have audit log about failure with
> transactionId and operation.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
