-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
_gdbm.error: Database needs recovery #1398
Labels
Comments
I have the same issue. Does somebody already know what the issue is? |
Same issue here |
I can't find how to avoid this issue, so I run a side-car container to periodically check and fix the database file if needed by using
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm running Flower service (flower==1.2.0) in K8s with replicas=1. The database file for Flower is maintained in K8s Persistent Volum:
From time to time, the Flower service crashes because of the corrupted database:
Expected behavior
The database corruption should never happen since the database file is only accessed by Flower service.
The text was updated successfully, but these errors were encountered: