You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by rn...@apache.org on 2020/12/15 21:21:55 UTC

[couchdb-documentation] 01/01: Revert "Suggested edit to make clear what a quorum actually represents. (#252)"

This is an automated email from the ASF dual-hosted git repository.

rnewson pushed a commit to branch revert-quorum-edit
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git

commit 2a80b50f782493abd36838c987f64d5b9852a44c
Author: Robert Newson <rn...@apache.org>
AuthorDate: Tue Dec 15 21:20:05 2020 +0000

    Revert "Suggested edit to make clear what a quorum actually represents. (#252)"
    
    This reverts commit 4eabf7978a61d4e4432cfd4f5e647179e39f3661.
    
    This notion of different quorums for doc read vs doc write is not true.
---
 src/cluster/theory.rst | 21 ++++++---------------
 1 file changed, 6 insertions(+), 15 deletions(-)

diff --git a/src/cluster/theory.rst b/src/cluster/theory.rst
index 3563c93..0ea50e8 100644
--- a/src/cluster/theory.rst
+++ b/src/cluster/theory.rst
@@ -32,21 +32,12 @@ As you see in ``etc/default.ini`` there is a section called ``[cluster]``
 When creating a database you can send your own values with request and
 thereby override the defaults in ``default.ini``.
 
-In clustered operation, a quorum must be reached before CouchDB returns a
-``200`` for a fetch, or ``201`` for a write operation. A quorum is defined as
-one plus half the number of "relevant copies". "Relevant copies" is defined
-slightly differently for read and write operations.
-
-For read operations, the number of relevant copies is the number of
-currently-accessible shards holding the requested data, meaning that in the case
-of a failure or network partition, the number of relevant copies may be lower
-than the number of replicas in the cluster.  The number of read copies can be
-set with the ``r`` parameter.
-
-For write operations the number of relevant copies is always ``n``, the number
-of replicas in the cluster.  For write operations, the number of copies can be
-set using the w parameter. If fewer than this number of nodes is available, a
-``202`` will be returned.
+The number of copies of a document with the same revision that have to be read
+before CouchDB returns with a ``200`` is equal to a half of total copies of
+the document plus one. It is the same for the number of nodes that need to
+save a document before a write is returned with ``201``. If there are less
+nodes than that number, then ``202`` is returned. Both read and write numbers
+can be specified with a request as ``r`` and ``w`` parameters accordingly.
 
 We will focus on the shards and replicas for now.