-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
create '_users' database for singleton mode:"The database could not be created, the file already exists. #4236
Comments
The distributed deploy command restart kernel and some containers cannot restart, so I try to redeploy from begin, then I got above issue. |
additional:
|
Moreover, when i first run
But if i ran it again, a different issue occured.
|
Just to confirm: you're running couchdb in a container and using the couchdb playbook? |
I found a potential problem with the couch playbook and will propose a patch that should address this symptom. |
I wonder if something like what we do in the kube couch-db init job might be useful? The idea is that after initialization completes, we create a marker table. Other jobs can then key on the existence of this table to know that the init job has completed. |
Environment details:
Steps to reproduce the issue:
The text was updated successfully, but these errors were encountered: