-
Notifications
You must be signed in to change notification settings - Fork 580
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
kafka: Usage manager bugfixes #9917
kafka: Usage manager bugfixes #9917
Conversation
/ci-repeat 2 skip-unit dt-repeat=50 tests/rptest/tests/usage_test.py::UsageTestCloudStorageMetrics.test_usage_manager_cloud_storage |
For those reviewing , this test was flaky because the admin.py class randomly chooses a node to query for usage_manager stats. The controller leader always had the correct results on it. The test has 30 seconds to complete so it has a moderate chance to grab the correct results from the follower leader. In the case it didn't it failed. |
/ci-repeat 2 skip-unit dt-repeat=50 tests/rptest/tests/usage_test.py |
- Cloud storage metrics were only reported correctly when queried on the leader node. - This change ensures that the metric when queried is saved in memory in the health_montior on followers - Fixes: redpanda-data#9702
- Not calling `co_await` on mutex::get_units means no lock is actually held. - Fixes: redpanda-data#9647
4ab12ae
to
9ded5ed
Compare
/ci-repeat 2 skip-unit dt-repeat=50 tests/rptest/tests/usage_test.py |
579b69a
to
0879019
Compare
/ci-repeat 2 skip-unit dt-repeat=50 tests/rptest/tests/usage_test.py |
/backport v23.1.x |
Fixes a bug where cloud storage metrics were only reported correctly when queried on the leader node.
Fixes a bug where multiple configuration updates would cause an inconsistency upon next reload of usage state
Backports Required
Release Notes
Bug Fixes