-
Notifications
You must be signed in to change notification settings - Fork 593
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
CI Failure (leader count on shard (2, 0) (3) is < 4
) in AutomaticLeadershipBalancingTest.test_automatic_rebalance
#17150
Labels
area/replication
auto-triaged
used to know which issues have been opened from a CI job
ci-failure
ci-rca/redpanda
CI Root Cause Analysis - Redpanda Issue
Comments
vbotbuildovich
added
auto-triaged
used to know which issues have been opened from a CI job
ci-failure
labels
Mar 16, 2024
michael-redpanda
changed the title
CI Failure (key symptom) in
CI Failure (Mar 19, 2024
AutomaticLeadershipBalancingTest.test_automatic_rebalance
leader count on shard (2, 0) (3) is < 4
) in AutomaticLeadershipBalancingTest.test_automatic_rebalance
1 similar comment
The test is failing because a newly restarted node is sending an incomplete health report (some partitions haven't started yet). I guess we can give newly restarted nodes a grace period and mute them for a bit before transferring leadership there (a good idea for other reasons as well). |
Merged
7 tasks
ztlpn
added a commit
to ztlpn/redpanda
that referenced
this issue
May 15, 2024
7 tasks
ztlpn
added a commit
to ztlpn/redpanda
that referenced
this issue
May 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/replication
auto-triaged
used to know which issues have been opened from a CI job
ci-failure
ci-rca/redpanda
CI Root Cause Analysis - Redpanda Issue
https://buildkite.com/redpanda/vtools/builds/12307
JIRA Link: CORE-1883
The text was updated successfully, but these errors were encountered: