-
Notifications
You must be signed in to change notification settings - Fork 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
Conflicted shards #4849
Comments
These conflicts shards typically are benign. They result from concurrent updates to To mitigate or stop the issue you can find the conflicted dbs and delete the conflicted revision. So if 2-abc... and 2-def are conflicted and 2-def is the actively used shard map, you can delete 2-abc by getting its rev and then issue a delete with rev = |
(sorry closed by accident) |
Thanks for your response @nickva Finding the conflicted DB seems like a hard task in a million-db cluster with a medium db creation/deletion rate. Maybe you have some hints on how to find them? |
in a remote shell to any node in the cluster run: |
We have used https://docs.couchdb.org/en/stable/replication/conflicts.html#finding-conflicted-documents-with-mango to find the conflicted databases. One interesting things is that we have conflicts for |
How can we do that?
|
The "4 conflicted shards in cluster" is referring to conflicts within the meta _dbs documents that define where the shards of databases should be, it is not reporting on the conflicted documents within your regular databases. the These are most likely by concurrent requests to create the same database, which is quite unusual. |
Yes, but
Thanks, by using |
Description
We have in the CouchDB logs some messages saying:
We are using many small databases created with a single shard (
q=1
). We don't know which shards are in this state, nor what we can do about that.Steps to Reproduce
We don't know how to reproduce.
Expected Behaviour
Well, if CouchDB could avoid to create conflicted shards, it would be nice. At least, some documentation for what to do in that case is expected.
Your Environment
Additional Context
The text was updated successfully, but these errors were encountered: