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

Unevenness error stop condition improvements/fixes #7408

Merged

Conversation

mmaslankaprv
Copy link
Member

@mmaslankaprv mmaslankaprv commented Nov 21, 2022

Improved handling of stop condition based on lack of partition balance improvement.

Backports Required

  • none - not a bug fix
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v22.3.x
  • v22.2.x
  • v22.1.x

UX Changes

Release Notes

Improvements

  • Improved handling of stop condition based on lack of partition balance improvement

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>
@mmaslankaprv mmaslankaprv modified the milestones: v22.2.8, v22.3.4 Nov 21, 2022
Copy link
Contributor

@VadimPlh VadimPlh left a 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

@mmaslankaprv mmaslankaprv merged commit f0a4ed9 into redpanda-data:dev Nov 21, 2022
@mmaslankaprv
Copy link
Member Author

/backport v22.3.x

@vbotbuildovich
Copy link
Collaborator

Oops! Something went wrong.

Workflow run logs.

@andrewhsu
Copy link
Member

/backport v22.3.4

@vbotbuildovich
Copy link
Collaborator

Failed to run cherry-pick command. I executed the below command:

git cherry-pick -x bbe9d84159dc9f30994c7b56b45c7c10c883ab46 4eb799cc3bf968b3073eacf1cd7ae7a1c55d8b75 f2d6b4d709f1f080142407ff2b7af136bf44843c

Workflow run logs.

@andrewhsu
Copy link
Member

andrewhsu commented Nov 21, 2022

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

@mmaslankaprv
Copy link
Member Author

/backport v22.3.4

@andrewhsu
Copy link
Member

fyi this PR seems like an improvement so i've added it as such in the PR body (it was blank before)

@BenPope
Copy link
Member

BenPope commented Apr 19, 2023

@BenPope BenPope modified the milestones: v22.2.8, v22.2.x-next Apr 19, 2023
@vshtokman vshtokman removed this from the v22.2.x-next milestone Apr 28, 2023
@vshtokman vshtokman added this to the v22.2.12 milestone Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants