Hi Carlos, yes …
The _all_docs, _changes, _view and _find endpoints do *not* apply any quorum to
their results. They generate a merged result set from exactly one copy of every
shard, and the copy that is selected is not always stable. So this is the
defined (if admittedly unexpected) behavior.
Hi guys.
I've been experimenting with operating a CouchDB 2.0 cluster and I've seen
the following unexpected behaviour.
Having a db with just one shard and just one repica, and a client that just
inserts a new document and reads /db/_all_docs on a loop every second (just
to simulate a controlled
