heshshark commented on issue #18105: URL: https://github.com/apache/hudi/issues/18105#issuecomment-3869833662
> kind of related to this fix: [#12150](https://github.com/apache/hudi/pull/12150) I don't believe PR #12150 can fix this issue. Here's my analysis: PR #12150 addresses write exceptions, but there are no write exception logs in our case. The rollback of instant 20260203180402381 was not caused by write failures. Instead, it appears to be caused by two startCommit() calls in rapid succession, where the second call's pre-commit cleanup (EAGER policy) rolled back the first instant. Critical unanswered question: Even if instant 20260203180402381 was rolled back, instant 20260203180404672 successfully committed and generated the corresponding parquet files. As long as those files existed, there should be no data loss. However, those parquet files were deleted (S3 logs show delete operations at 18:06 and 18:10). Finding out why these files were deleted is another breakthrough point for solving this issue. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
