[
https://issues.apache.org/jira/browse/HUDI-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646865#comment-17646865
]
Ethan Guo commented on HUDI-5169:
---------------------------------
Let's say RB2 is intended to roll back C1. The rollback process first deletes
the data files, C1.commit, C1.commit.requested, and C1.commit.inflight, before
transitioning the RB2 from inflight to complete.
In case the rollback removed the commit to be rolled back, but failed to
complete, i.e., RB2 fails just before being transitioned to complete and after
deleting all data and commit files for C1, next time writer still retries the
same rollback (RB2). There shouldn't be any problem.
> Re-attempt failed rollback (regular commits, clustering) and get it to
> completion
> ---------------------------------------------------------------------------------
>
> Key: HUDI-5169
> URL: https://issues.apache.org/jira/browse/HUDI-5169
> Project: Apache Hudi
> Issue Type: Improvement
> Components: writer-core
> Reporter: sivabalan narayanan
> Assignee: Ethan Guo
> Priority: Blocker
> Fix For: 0.13.0
>
>
> If rollback removed the commit to be rolled back, but failed to complete, we
> may never get to complete it. bcoz, the original commit that needs to be
> rolledback is not seen in the timeline.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
