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
The bug was found under dledger mode and it should reproduce under normal commitLog.
The MessageDispatcherImpl didn't release the refCount of mapped file (DefaultMappedFile or DefaultMmapFile) correctly when diapatch was held, which may cause the refered commitLog undeleted.
Steps to Reproduce
Enable tiered store, produce message under low rate which cause MessageDispatcher#dispatch hold at least once.
When CleanCommitLogService#deleteExpiredFiles deleting the held file, the log highlighted below should be shown.
What Did You Expect to See?
The expired commitLog should be deleted correctly.
What Did You See Instead?
Unexpected warn log.
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
MessageDispatcherImpl
didn't release therefCount
of mapped file (DefaultMappedFile
orDefaultMmapFile
) correctly when diapatch was held, which may cause the refered commitLog undeleted.Steps to Reproduce
MessageDispatcher#dispatch
hold at least once.CleanCommitLogService#deleteExpiredFiles
deleting the held file, the log highlighted below should be shown.What Did You Expect to See?
The expired commitLog should be deleted correctly.
What Did You See Instead?
Unexpected warn log.
Additional Context
No response
The text was updated successfully, but these errors were encountered: