You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "hudi-bot (via GitHub)" <gi...@apache.org> on 2025/11/30 11:25:17 UTC
[I] Fix leftover/lingering rollbacks for table services [hudi]
hudi-bot opened a new issue, #16792:
URL: https://github.com/apache/hudi/issues/16792
when a table service fails, and is re-attempted, we trigger a rollback followed by re-attempting the table service. w/ clustering, we have a way to nuke the entire clustering plan. [https://github.com/apache/hudi/blob/baf141abbd6da022c66fa518588e34452a6902b4/hudi-client/hudi-spark-client/src/main/java/org/apache/hudi/table/action/commit/BaseSparkCommitActionExecutor.java#L142]
but there are chances we end up in below state
t6.rc.req
t6.rc.inflight
// trigger rollback.
t7.rb.req
t7.rb.inflig
delete all data files from t6.rc
write to metadata table
delete t6.rc* files from timeline
and we crash.
So, we might have a lingering rollback plan t7.rb.req and t7.rb.inflight in the timeline forever.
This might only be an issue when we try to nuking the entire plan. Otherwise, t6.rc.req will never be cleaned up and next attempt will retry it.
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-8886
- Type: Bug
- Fix version(s):
- 1.1.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Fix leftover/lingering rollbacks for table services [hudi]
Posted by "rangareddy (via GitHub)" <gi...@apache.org>.
rangareddy commented on issue #16792:
URL: https://github.com/apache/hudi/issues/16792#issuecomment-5391410734
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-8886).
**Findings: still open.**
No commit referencing HUDI-8886 exists in the tree, so nothing has landed under this ticket's key.
The description here is substantive and self-describing, so this is workable as written - it is the absence of an owner rather than of a specification.
Keeping this open.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org