zuston opened a new issue, #3562: URL: https://github.com/apache/fluss/issues/3562
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Fluss version 0.9.0 (latest release) ### Please describe the bug 🐞 The bug is caused by overlapping tiering rounds for the same table. When an old round is force-finished due to max duration, its results may still be pending in the committer. Meanwhile, the enumerator can start and assign a new round for the same table. Since TableBucketWriteResult does not carry an epoch/round id, the committer groups results only by table and bucket. So results from the old round and the new round can be mixed together. If both contain the same bucket, the committer treats them as duplicate write results and fails. <img width="1648" height="311" alt="Image" src="https://github.com/user-attachments/assets/77d1db17-dee9-416f-a2c7-f0d4c1162e48"; /> <img width="1624" height="455" alt="Image" src="https://github.com/user-attachments/assets/d2a7f915-0c9f-4b6b-8a57-e18b8d9ff538"; /> ### Solution _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
