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

[Feature] Auto-recover if database directory is locked #124

Open
amshuman-kr opened this issue Dec 3, 2020 · 0 comments
Open

[Feature] Auto-recover if database directory is locked #124

amshuman-kr opened this issue Dec 3, 2020 · 0 comments
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) priority/3 Priority (lower number equals higher priority)

Comments

@amshuman-kr
Copy link
Collaborator

amshuman-kr commented Dec 3, 2020

Feature (What you would like to be added):
In some infrastructures (Azure), abnormal termination of etcd container/pod leads to the database directory lock not being released and prevents the backup-restore to hang while opening the database for verification on etcd container restart.

We should try to detect this scenario and try to recover from it automatically.

Motivation (Why is this needed?):
This happens rarely (so far only a couple of times in Azure) but requires manual intervention. Typically, a pod restart resolves the issue. But we should try and automate this.

Approach/Hint to the implement solution (optional):
Typically, a pod restart resolves the issue.

@amshuman-kr amshuman-kr added the kind/enhancement Enhancement, improvement, extension label Dec 3, 2020
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 22, 2021
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Mar 24, 2022
@abdasgupta abdasgupta added priority/4 Priority (lower number equals higher priority) priority/3 Priority (lower number equals higher priority) and removed priority/4 Priority (lower number equals higher priority) labels Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) priority/3 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

3 participants