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
When topics are created and deleted frequently, a JVM crash occurred. Analysis revealed that when a topic is deleted, the file is unmapped. During this time, the ReputMessageService dispatches the consumeQueue and writes to the mmap file, which may cause the JVM to crash.
Steps to Reproduce
Start the broker
Start the producer to send continuously
While sending, use the admin to delete the topic
Finally, the broker crashes, and the exception stack trace is consistent with the one online
What Did You Expect to See?
No JVM crash
What Did You See Instead?
JVM crash
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
All platform
RocketMQ version
4.9.3 ~ lastest, after #3657
JDK Version
All versions
Describe the Bug
When topics are created and deleted frequently, a JVM crash occurred. Analysis revealed that when a topic is deleted, the file is unmapped. During this time, the ReputMessageService dispatches the consumeQueue and writes to the mmap file, which may cause the JVM to crash.
Steps to Reproduce
Start the broker
Start the producer to send continuously
While sending, use the admin to delete the topic
Finally, the broker crashes, and the exception stack trace is consistent with the one online
What Did You Expect to See?
No JVM crash
What Did You See Instead?
JVM crash
Additional Context
No response
The text was updated successfully, but these errors were encountered: