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
Linux 4.19
RocketMQ version
branch: develop latest
JDK Version
JDK11
Describe the Bug
In the tiered storage upload process, there are obvious issues with error handling for failed uploads:
When cq fails to upload, data correction needs to be done based on the current storage position / file length.
Retrieving positions from distributed storage can still fail, with -1 and 0 used to differentiate.
-1 indicates failure due to network or other reasons, and 0 indicates that the file does not exist or has a length of zero.
The control flow of the buffer list during upload is overly complicated, and a new approach is simpler and more reliable.
Adding position comparison logs to track failed requests.
Before Creating the Bug Report
Runtime platform environment
Linux 4.19
RocketMQ version
branch: develop latest
JDK Version
JDK11
Describe the Bug
In the tiered storage upload process, there are obvious issues with error handling for failed uploads:
-1 indicates failure due to network or other reasons, and 0 indicates that the file does not exist or has a length of zero.
分级存储上传流程中,对于上传失败的错误处理存在明显问题:
-1 表示因为网络或其他原因失败,0 表示文件不存在或者长度为 0。
Steps to Reproduce
As long as the cq upload fails, the build process will have problems.
What Did You Expect to See?
Construct cq and commitlog correctly.
What Did You See Instead?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered: