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

Maintenance mode test fixes #21435

Merged
merged 3 commits into from
Jul 17, 2024
Merged

Maintenance mode test fixes #21435

merged 3 commits into from
Jul 17, 2024

Conversation

ztlpn
Copy link
Contributor

@ztlpn ztlpn commented Jul 16, 2024

Please see commit descriptions for explanations.

Fixes #20592
Fixes #20297
Fixes #19928
Fixes #19926
Fixes #13650

Backports Required

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

Release Notes

  • none

ztlpn added 3 commits July 16, 2024 21:48
Previously when this test was running in CI there were not a lot of partitions (12)
and the leadership balancer could mute them all after several ticks (it mutes the
partitions that it moves). After that it cannot take any further action for some time
and the node that comes out of the maintenance mode won't acquire any new leaders.

Increase the number of partitions in the test to avoid that.

Fixes: redpanda-data#13650
Previously we waited for 50 seconds in total to ensure that the node has
some leaders. If it hadn't acquired any leaders "naturally", this was
not enough because the leadership balancer needs at least 1 minute to
unmute just restarted nodes and perform another tick.
@bharathv bharathv merged commit 015afa7 into redpanda-data:dev Jul 17, 2024
21 checks passed
@vbotbuildovich
Copy link
Collaborator

/backport v24.1.x

@vbotbuildovich
Copy link
Collaborator

/backport v23.3.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment