couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From woh...@apache.org
Subject [couchdb-documentation] branch master updated: Clean up wording in "Add, then delete" section (#192)
Date Wed, 01 Nov 2017 20:42:31 GMT
This is an automated email from the ASF dual-hosted git repository.

wohali pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git


The following commit(s) were added to refs/heads/master by this push:
     new 279d117  Clean up wording in "Add, then delete" section (#192)
279d117 is described below

commit 279d1177887882844f5fa85214fbbe0df9510a0b
Author: Daniel Roberts <droberts@dimagi.com>
AuthorDate: Wed Nov 1 13:42:30 2017 -0700

    Clean up wording in "Add, then delete" section (#192)
    
    * Clean up wording in "Add, then delete" section
---
 src/cluster/sharding.rst | 28 +++++++++++++++++-----------
 1 file changed, 17 insertions(+), 11 deletions(-)

diff --git a/src/cluster/sharding.rst b/src/cluster/sharding.rst
index b2ef4ea..5ad998a 100644
--- a/src/cluster/sharding.rst
+++ b/src/cluster/sharding.rst
@@ -198,19 +198,25 @@ Moving Shards
 Add, then delete
 ----------------
 
-In the world of CouchDB there is no such thing as moving. You can add a new
-replica to a shard and then remove the old replica, thereby creating the
-illusion of moving. If you try to uphold this illusion with a database that have
-``n=1``, you might find yourself in the following scenario:
-
-#. Copy the shard to a new node.
+In the world of CouchDB there is no such thing as "moving" shards, only adding
+and removing shard replicas.
+You can add a new replica of a shard and then remove the old replica,
+thereby creating the illusion of moving.
+If you do this for a database that has ``n=1``,
+you might be caught by the following mistake:
+
+#. Copy the shard onto a new node.
 #. Update the metadata to use the new node.
 #. Delete the shard on the old node.
-#. Lose all writes made between 1 and 2.
-
-As the reality "I added a new replica of the shard X on node Y and then I waited
-for them to sync, before I removed the replica of shard X from node Z." is a bit
-tedious, people and this documentation tend to use the illusion of moving.
+#. Oh, no!: You have lost all writes made between 1 and 2.
+
+To avoid this mistake, you always want to make sure
+that both shards have been live for some time
+and that the shard on your new node is fully caught up
+before removing a shard on an old node.
+Since "moving" is a more conceptually (if not technically)
+accurate description of what you want to do,
+we'll use that word in this documentation as well.
 
 Moving
 ------

-- 
To stop receiving notification emails like this one, please contact
['"commits@couchdb.apache.org" <commits@couchdb.apache.org>'].

Mime
View raw message