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.

Sign up for GitHub

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

Jump to bottom

Leader election after node reboot fails #467

Closed
anishakj opened this issue Apr 25, 2022 · 0 comments · Fixed by #468
Closed

Leader election after node reboot fails #467

anishakj opened this issue Apr 25, 2022 · 0 comments · Fixed by #468
Assignees
@anishakj
Milestone
Release 0.2.14

Comments

@anishakj
Copy link
Contributor

Description

In VMware cluster, some pods are stuck in ProviderFailed state, and leader election function, provided by operator SDK, is unable to process that, so new pods are stuck in wait cycle.
Fix scans owners of leader lock config map, and deletes pods in ProviderFailed status.

Importance

must-have

Location

main.go

Suggestions for an improvement

Customise leader.Become function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@anishakj anishakj

Labels
None yet
Projects
None yet
Milestone
Release 0.2.14
Development

Successfully merging a pull request may close this issue.

Issue 467: Fixing Leader election failure pravega/zookeeper-operator
1 participant
@anishakj