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

[v23.3.x] c/topics_dispatcher: do not guesstimate leader ids #16236

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #15678
Fixes: #16235,

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>
(cherry picked from commit 3e86234)
Signed-off-by: Michal Maslanka <michal@redpanda.com>
(cherry picked from commit 8f81843)
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>
(cherry picked from commit 86d583b)
Signed-off-by: Michal Maslanka <michal@redpanda.com>
(cherry picked from commit 763c0ac)
Signed-off-by: Michal Maslanka <michal@redpanda.com>
(cherry picked from commit 5bf2a27)
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>
(cherry picked from commit fea4f6a)
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>
(cherry picked from commit 3b2eac5)
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>
(cherry picked from commit 6823527)
@vbotbuildovich vbotbuildovich added this to the v23.3.x-next milestone Jan 23, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Jan 23, 2024
@piyushredpanda piyushredpanda marked this pull request as ready for review January 23, 2024 13:24
@piyushredpanda piyushredpanda modified the milestones: v23.3.x-next, v23.3.4 Jan 24, 2024
@piyushredpanda piyushredpanda requested a review from a team January 24, 2024 13:02
@travisdowns travisdowns requested review from a team and travisdowns and removed request for a team January 24, 2024 13:05
@piyushredpanda piyushredpanda removed the request for review from travisdowns January 24, 2024 13:08
@savex
Copy link
Contributor

savex commented Jan 24, 2024

/ci-repeat

@piyushredpanda piyushredpanda merged commit f9c2a01 into redpanda-data:v23.3.x Jan 25, 2024
17 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[v23.3.x] CI Failure (RpkException) in RpkToolTest.test_consume_from_partition
4 participants