[
https://issues.apache.org/jira/browse/HDDS-10822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850831#comment-17850831
]
Hemant Kumar commented on HDDS-10822:
-------------------------------------
[~sumitagrawl],
HDDS-10295 can be used if the next transaction from the last applied
transaction (from transactionInfoTable) is failing. But if there is a gap
between the failed transaction and the last applied transaction because the
double buffer does batch flush, we need this tool.
Talking about the {*}transactionId{*}, you can get it from Ratis log using
"{*}ozone debug ratislogparser{*}" command.
We can discuss if it makes sense to add it to audit logs. It is redundant
information to me.
> 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]
