[
https://issues.apache.org/jira/browse/HDDS-10822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850591#comment-17850591
]
Sumit Agrawal commented on HDDS-10822:
--------------------------------------
[~hemantk]
https://issues.apache.org/jira/browse/HDDS-10295 provides mechanism to update
the transaction ID to transaction info as recovery.
To identify the transaction causing crash, we should add audit log for these
failure scenario, so that same transaction Id can be updated to skip same.
For more than one failing transaction, till its executed and failed, this can
not be ensured. so it should skip one by one for each failure with failure
analysis.
IMO, having *audit log with transactionID* for all cases – exceptionally failed
transaction and other executed successful/failed request will do this job.
Steps:
* Transaction failed for index as in audit log
* Update transaction info for the index (skip) and start again
* If failed again for next index, repeat above steps
> Provide a repair tool to omit a raft log
> ----------------------------------------
>
> Key: HDDS-10822
> URL: https://issues.apache.org/jira/browse/HDDS-10822
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Hemant Kumar
> Priority: Major
>
> Sometimes we have seen cases when a particular raft log can't be applied
> because of some issue on OM restart. We should come up with some repair tool
> or mechanize to skip that transaction so that we can move forward and bring
> up the service back.
> In the simple case when transaction in transactionInfoTable is just a
> transaction behind than to the raft transaction it is failing for, we can use
> HDDS-8097 but for the scenario when gap between the transaction in
> transactionInfoTable and failing transaction is more than one, we will need
> this tool to skip particular raft log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
