-
Notifications
You must be signed in to change notification settings - Fork 586
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/topics_dispatcher: do not guesstimate leader ids #15678
c/topics_dispatcher: do not guesstimate leader ids #15678
Conversation
I wonder what was the original motivation? Can this change lead to undesirable effects like health status flip-flop? |
29e6b56
to
52542fd
Compare
Original motivation comes from the times when we didn't have infrastructure to wait for topic creation. We wanted to speed up metadata propagation. Now since the necessary API is there we do not need to estimate leaders anymore. |
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/42866#018c6dda-8e8d-4d59-a294-1244e404ea64 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/42887#018c6e8e-3532-4bc5-a584-95dfe2f121b0 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/42887#018c6eb5-b6a0-40a9-a2ea-ad13548af0d7 |
823d161
to
f8a7e7d
Compare
new failures in https://buildkite.com/redpanda/redpanda/builds/42970#018c7dc6-d933-48d0-9eb7-f5b7f6495974:
new failures in https://buildkite.com/redpanda/redpanda/builds/43118#018c86c7-e656-4f44-a679-9f2fcbcf12d4:
new failures in https://buildkite.com/redpanda/redpanda/builds/43139#018c876b-b5ff-45c1-bc68-e294080f1ca2:
new failures in https://buildkite.com/redpanda/redpanda/builds/43139#018c877a-c983-46ac-bb2f-53ef24dc80f1:
new failures in https://buildkite.com/redpanda/redpanda/builds/43209#018c8c1a-5875-4980-b82e-db682607291b:
new failures in https://buildkite.com/redpanda/redpanda/builds/43209#018c8c1a-5878-4570-82f5-19a0a60c0b95:
new failures in https://buildkite.com/redpanda/redpanda/builds/43209#018c8c1f-4f7d-41d7-a61c-1166074bd617:
new failures in https://buildkite.com/redpanda/redpanda/builds/43209#018c8c1a-587e-45dd-beeb-9f9d0bd3c33f:
new failures in https://buildkite.com/redpanda/redpanda/builds/43209#018c8c1f-4f7a-40e6-bd72-a1dad44b7057:
|
86a4b2f
to
9569e0b
Compare
dd3d7a6
to
502f1fe
Compare
/ci-repeat 1 |
Updating leadership metadata before the topic is ready to serve traffic is not desired. It prevents waiting for leader to be reported by raft group when it is actually ready. Signed-off-by: Michal Maslanka <michal@redpanda.com>
Signed-off-by: Michal Maslanka <michal@redpanda.com>
Instead of returning `-1` indicating that there is an ongoing leader election we return randomly selected node as a partition leader. This is much less interrupting for the client as it simply forces it to refresh metadata. Some clients do not tolerate `-1` returned from Metadata handler and simply stop working. Signed-off-by: Michal Maslanka <michal@redpanda.com>
Signed-off-by: Michal Maslanka <michal@redpanda.com>
Signed-off-by: Michal Maslanka <michal@redpanda.com>
The metadata dissemination test must account for exponential backoff which may be longer than used 10 seconds timeout. Now as we do not update leaders table after topic create command is applied we need to wait for the request to be delivered to joining node. Signed-off-by: Michal Maslanka <michal@redpanda.com>
The consumer group recovery test doesn't do any validation if offset listing was successful. Disabling leader balancer will make the test more stable before we introduce validation in recovery tool (now the tool assumes that user is going to review offsets listing). Signed-off-by: Michal Maslanka <michal@redpanda.com>
6e0f12a
to
5d19867
Compare
Wait for at least some of the messages to be successfully written to topic before starting consumers to prevent them trying to read empty partition. Signed-off-by: Michal Maslanka <michal@redpanda.com>
5d19867
to
6823527
Compare
known unrelated ci-failure: #15679 |
/backport v23.3.x |
/backport v23.2.x |
Failed to create a backport PR to v23.2.x branch. I tried:
|
Updating leadership metadata before the topic is ready to serve traffic is not desired. It prevents waiting for leader to be reported by raft group when it is actually ready.
Fixes: #14673
Backports Required
Release Notes