-
Notifications
You must be signed in to change notification settings - Fork 592
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
c/config_manager: populate configuration status on members notification #13964
Conversation
When member is added to the cluster `cluster::configuration_manager` should be immediately aware of it instead of waiting for the first status update. Wired up cluster member added notification to update cluster configuration reconciliation status with initial state for joining member. Fixes: redpanda-data#13497 Fixes: redpanda-data#13503 Signed-off-by: Michal Maslanka <michal@redpanda.com>
010561e
to
57c8d7a
Compare
ducktape was retried in job https://buildkite.com/redpanda/redpanda/builds/38438#018b0409-c4a1-412b-a0cd-e42efb9d19f3 |
the debug build has this failure in kafka_server_rpfixture.fetch_one": seastar::timed_out_error: timedout |
The error is unrelated i will submit a PR fixing it |
/backport v23.2.x |
/backport v23.1.x |
Oops! Something went wrong. |
Failed to create a backport PR to v23.1.x branch. I tried:
|
When member is added to the cluster
cluster::configuration_manager
should be immediately aware of it instead of waiting for the first status update.Wired up cluster member added notification to update cluster configuration reconciliation status with initial state for joining member.
Fixes: #13497
Fixes: #13503
Backports Required
Release Notes