swuferhong opened a new issue, #2766: URL: https://github.com/apache/fluss/issues/2766
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Fluss version main (development) ### Please describe the bug 🐞 In `LogTieringTask#runOnce()`, the method `copyLogSegmentFilesToRemote` copies candidate log segments to remote storage sequentially. If any single segment copy fails (e.g., due to rate limiting or a transient network error), a `RemoteStorageException` is thrown and propagated to the caller, causing the entire `runOnce() ` method to skip the commit phase. This means all previously successful segment uploads in the same batch are wasted — they are never committed to the remote log manifest and become orphaned files on remote storage. For example, if there are 10 candidate segments and the 6th fails due to rate limiting, the first 5 segments that were already successfully uploaded will not be committed and their work is lost. ### Solution _No response_ ### Are you willing to submit a PR? - [ ] 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]
