We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
all
latest
11
Timing metrics will not be cleaned when topics are deleted. it's because that the cleanMetrics task is not started.
create topic, send timing msg, then delete the topic, you will see that metric will not be cleaned.
the timing metrics should be cleaned.
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
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
RocketMQ version
latest
JDK Version
11
Describe the Bug
Timing metrics will not be cleaned when topics are deleted.
it's because that the cleanMetrics task is not started.
Steps to Reproduce
create topic, send timing msg, then delete the topic, you will see that metric will not be cleaned.
What Did You Expect to See?
the timing metrics should be cleaned.
What Did You See Instead?
create topic, send timing msg, then delete the topic, you will see that metric will not be cleaned.
Additional Context
No response
The text was updated successfully, but these errors were encountered: