-
Notifications
You must be signed in to change notification settings - Fork 552
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
Unevenness error stop condition improvements/fixes #7408
Unevenness error stop condition improvements/fixes #7408
Conversation
When update is finished the error should be reset so that the next update rebalancing is not influenced with the result of previous one. Signed-off-by: Michal Maslanka <michal@redpanda.com>
As the unevenness error is in the range of 0.0 to 1.0 we must use floating point to make calculations accurate. Signed-off-by: Michal Maslanka <michal@redpanda.com>
Signed-off-by: Michal Maslanka <michal@redpanda.com>
7099602
to
f2d6b4d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
To check we can use chaos tx-single-reads-writes / java / recycle all
Should not contain any UNKNOWN error
/backport v22.3.x |
Oops! Something went wrong. |
/backport v22.3.4 |
Failed to run cherry-pick command. I executed the below command:
|
with the codebase currently in v22.3.x branch, backport of this PR causes conflicts. it seems like the conflicts can be avoided if PR #7388 is first backported to v22.3.x branch. backport attempted and created: PR #7416 |
/backport v22.3.4 |
fyi this PR seems like an improvement so i've added it as such in the PR body (it was blank before) |
Please backport to v22.2.x - https://buildkite.com/redpanda/redpanda/builds/27435#0187967e-8fba-485b-b8ef-ac14b71bd2c9 |
Improved handling of stop condition based on lack of partition balance improvement.
Backports Required
UX Changes
Release Notes
Improvements