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

do not step down when replicating configuration failed #4352

Closed
andrewhsu opened this issue Apr 20, 2022 · 3 comments · Fixed by #4342
Closed

do not step down when replicating configuration failed #4352

andrewhsu opened this issue Apr 20, 2022 · 3 comments · Fixed by #4342
Assignees
Labels
kind/bug Something isn't working

Comments

@andrewhsu
Copy link
Member

In Redpanda leader replicates a configuration after successful vote
round. Configuration replication success isn't required for the node to
hold the leadership.

In some scenarios, when majority of followers are behind the leader and
need recovery, configuration replication may timeout. This doesn't mean
however that leader should step down. In order to maintain leadership it
should continue recovering followers and step down only if there are no
heartbeat responses from majority of the followers.

@andrewhsu
Copy link
Member Author

/backport v21.11.x

@andrewhsu
Copy link
Member Author

This issue is addressed because PR #4342 merged.

@dotnwat
Copy link
Member

dotnwat commented Apr 26, 2022

/backport v22.1.x

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants