cassandra git commit: Doc change: Describe replacement cases based on CASSANDRA-8523 and CASSANDRA-12344

[jj...@apache.org]

Repository: cassandra
Updated Branches:
  refs/heads/trunk e6c2ae1f3 -> 33ca487f9


Doc change: Describe replacement cases based on CASSANDRA-8523 and CASSANDRA-12344

Closes #145

Patch by Kurt Greaves; Reviewed by Jeff Jirsa for CASSANDRA-8523


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/33ca487f
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/33ca487f
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/33ca487f

Branch: refs/heads/trunk
Commit: 33ca487f95665b577730a409e7168feb99d3cbf9
Parents: e6c2ae1
Author: kurt <ku...@instaclustr.com>
Authored: Tue Aug 29 03:36:12 2017 +0000
Committer: Jeff Jirsa <jj...@apple.com>
Committed: Tue Aug 29 22:17:46 2017 -0700

----------------------------------------------------------------------
 doc/source/operating/topo_changes.rst | 19 ++++++++++++-------
 1 file changed, 12 insertions(+), 7 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cassandra/blob/33ca487f/doc/source/operating/topo_changes.rst
----------------------------------------------------------------------
diff --git a/doc/source/operating/topo_changes.rst b/doc/source/operating/topo_changes.rst
index c42708e..6c8f8ec 100644
--- a/doc/source/operating/topo_changes.rst
+++ b/doc/source/operating/topo_changes.rst
@@ -98,16 +98,21 @@ Replacing a dead node
 
 In order to replace a dead node, start cassandra with the JVM startup flag
 ``-Dcassandra.replace_address_first_boot=<dead_node_ip>``. Once this property is enabled the node starts in a hibernate
-state, during which all the other nodes will see this node to be down.
+state, during which all the other nodes will see this node to be DOWN (DN), however this node will see itself as UP 
+(UN). Accurate replacement state can be found in ``nodetool netstats``.
 
-The replacing node will now start to bootstrap the data from the rest of the nodes in the cluster. The main difference
-between normal bootstrapping of a new node is that this new node will not accept any writes during this phase.
+The replacing node will now start to bootstrap the data from the rest of the nodes in the cluster. A replacing node will
+only receive writes during the bootstrapping phase if it has a different ip address to the node that is being replaced. 
+(See CASSANDRA-8523 and CASSANDRA-12344)
 
-Once the bootstrapping is complete the node will be marked "UP", we rely on the hinted handoff's for making this node
-consistent (since we don't accept writes since the start of the bootstrap).
+Once the bootstrapping is complete the node will be marked "UP". 
 
-.. Note:: If the replacement process takes longer than ``max_hint_window_in_ms`` you **MUST** run repair to make the
-   replaced node consistent again, since it missed ongoing writes during bootstrapping.
+.. Note:: If any of the following cases apply, you **MUST** run repair to make the replaced node consistent again, since 
+    it missed ongoing writes during/prior to bootstrapping. The *replacement* timeframe refers to the period from when the
+    node initially dies to when a new node completes the replacement process.
+
+    1. The node is down for longer than ``max_hint_window_in_ms`` before being replaced.
+    2. You are replacing using the same IP address as the dead node **and** replacement takes longer than ``max_hint_window_in_ms``.
 
 Monitoring progress
 ^^^^^^^^^^^^^^^^^^^


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org