You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
Any
RocketMQ version
develop
JDK Version
1.8
Describe the Bug
Current tiered storage will call FileSegment#commitAsync actively if the appended file is full, but ignoring the commit result, which may cause the last part of messages will never be uploaded.
Steps to Reproduce
Running broker and enable tiered storage, waiting until the last part of a commit log file is commit and failed.
What Did You Expect to See?
Messages that failed to be committed should be committed again.
What Did You See Instead?
The messages will not be commit ever.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
Any
RocketMQ version
develop
JDK Version
1.8
Describe the Bug
Current tiered storage will call
FileSegment#commitAsync
actively if the appended file is full, but ignoring the commit result, which may cause the last part of messages will never be uploaded.Steps to Reproduce
Running broker and enable tiered storage, waiting until the last part of a commit log file is commit and failed.
What Did You Expect to See?
Messages that failed to be committed should be committed again.
What Did You See Instead?
The messages will not be commit ever.
Additional Context
No response
The text was updated successfully, but these errors were encountered: