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 #397

Closed
anishakj opened this issue Oct 4, 2021 · 0 comments · Fixed by #396
Closed

Leader election after node reboot fails #397

anishakj opened this issue Oct 4, 2021 · 0 comments · Fixed by #396
Assignees
@anishakj
Milestone
Release 0.2.14

Comments

@anishakj
Copy link
Contributor

anishakj commented Oct 4, 2021

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

cmd/manager/main.go

Suggestions for an improvement

Customise the leader.Become function of operator-sdk to include pre-checks
@anishakj anishakj self-assigned this Oct 4, 2021
@anishakj anishakj mentioned this issue Oct 4, 2021
Merged
@anishakj anishakj changed the title Leader election after node fails Leader election after node reboot fails Oct 4, 2021
@anishakj anishakj added this to the Release 0.2.14 milestone May 5, 2022
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.

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