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

[Enhancement] Optimize the metric calculation logic of the time wheel #8127

Open
2 of 3 tasks
3424672656 opened this issue May 13, 2024 · 0 comments · May be fixed by #8128
Open
2 of 3 tasks

[Enhancement] Optimize the metric calculation logic of the time wheel #8127

3424672656 opened this issue May 13, 2024 · 0 comments · May be fixed by #8128

Comments

@3424672656
Copy link
Contributor

3424672656 commented May 13, 2024

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

Centos

RocketMQ version

develop

JDK Version

11

Describe the Bug

In each round of fetching an element, each element's message is a type, each message is addmetric() logic, the metric will fluctuate, but the final result is correct, after optimization only need to do addmetric once
768e059594335713a7f0670ea1b6128

33a27c1fb29ae14b983b7d97a9ba251

Steps to Reproduce

Use arrays for correct calculations for each round of placement

What Did You Expect to See?

metric is correctly

What Did You See Instead?

metric is incorrectly

Additional Context

No response

@3424672656 3424672656 changed the title [Bug] The metric of the time wheel was incorrectly calculated [Enhancement] Optimize the metric calculation logic of the time wheel May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant