-
Notifications
You must be signed in to change notification settings - Fork 589
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 decommissioning stopped making progress in NodesDecommissioningTest.test_flipping_decommission_recommission
#8621
Labels
area/replication
ci-failure
kind/bug
Something isn't working
sev/low
Bugs which are non-functional paper cuts, e.g. typos, issues in log messages
Comments
6 tasks
Marking as |
mmaslankaprv
added
the
sev/low
Bugs which are non-functional paper cuts, e.g. typos, issues in log messages
label
Feb 7, 2023
6 tasks
7 tasks
on (amd64, container) in job https://buildkite.com/redpanda/redpanda/builds/24612#0186bfbc-2e49-4641-9929-f97f0b7364a7 |
7 tasks
7 tasks
7 tasks
7 tasks
Not seen in 30 days, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/replication
ci-failure
kind/bug
Something isn't working
sev/low
Bugs which are non-functional paper cuts, e.g. typos, issues in log messages
https://buildkite.com/redpanda/redpanda/builds/22277#01860dcb-5c6c-45d2-9481-503b7fbbd528
The reason is that decommissioning for node 1 stopped making progress config is that
raft_learner_recovery_rate
is set to1
. The test last sets it to104857600
before we start checking for progress. However, if we look at the last couple of config upserts we can see that the config version when we set it to104857600
is older than the config version when it previously set it to1
It's clear from the RP node logs that config version 16 with
raft_learner_recovery_rate
=1
is the one that is eventually replicated to every node. I.e, the last log message I see in every node from theconfig_frontend
andconfig_manager
is similar to below;The text was updated successfully, but these errors were encountered: