Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Deleting ConsumeQueue files may cause JVM crashes #8405

Closed
3 tasks done
RongtongJin opened this issue Jul 19, 2024 · 0 comments · Fixed by #8403
Closed
3 tasks done

[Bug] Deleting ConsumeQueue files may cause JVM crashes #8405

RongtongJin opened this issue Jul 19, 2024 · 0 comments · Fixed by #8403

Comments

@RongtongJin
Copy link
Contributor

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
image
image

What Did You Expect to See?

No JVM crash

What Did You See Instead?

JVM crash

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant