Skip to content

KAFKA-18874: Fix KRaft controller registration retry on timeout #19321

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

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

fonaid
Copy link
Contributor

@fonaid fonaid commented Mar 31, 2025

There is a flag which is set when scheduling KRaft controller
registration request to be send. When a timeout occurs while the request
is in the queue but not yet sent, this flag is not deleted and thus the
registration request is not rescheduled. This patch addresses the above
issue by setting the flag to false on timeout.

@github-actions github-actions bot added triage PRs from the community core Kafka Broker small Small PRs labels Mar 31, 2025
Copy link

github-actions bot commented Apr 8, 2025

A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.

Copy link

A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-approved core Kafka Broker needs-attention small Small PRs triage PRs from the community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants