Skip to content

Commit 3e0b02f

Browse files
authored
DOC-12926--8.0--Feedback-on-Nodes--Couchbase-Docs (#4092)
1 parent 04a5b07 commit 3e0b02f

1 file changed

Lines changed: 19 additions & 3 deletions

File tree

modules/learn/pages/clusters-and-availability/removal.adoc

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ However, removal should be used only when all nodes in the cluster are responsiv
1414
Removal essentially means using xref:learn:clusters-and-availability/rebalance.adoc[Rebalance] to redistribute data across a subset of pre-existing cluster-nodes.
1515
It can be performed with the UI, the CLI, or the REST API.
1616
When the CLI or REST API is used, a single command initiates a rebalance, specifying which nodes are to be excluded.
17-
When the UI is used, nodes to be removed are first identified, then rebalance is initiated.
17+
When the UI is used, nodes to be removed are first identified; then rebalance is initiated.
1818
When the rebalance is complete, the _cluster map_ is correspondingly updated and distributed to clients.
1919
The process occurs while the cluster continues to service requests for data.
2020

@@ -74,7 +74,7 @@ As Table 1 shows, each of the four nodes takes a roughly equal share of the buck
7474
It also takes a roughly equal share of the replica bucket-items, kept in _replica_ vBuckets.
7575
Since the bucket has two replicas, the ratio of _active_ to _replica_ items, both on each node and in the total for the cluster, is approximately _1:2_.
7676

77-
Table 2 shows the results on the cluster of the removal of node 4 and subsequent rebalance.
77+
Table 2 shows the results on the cluster when node 4 is removed and the cluster is rebalanced.
7878

7979
.Three Surviving Data Service Nodes, One Bucket with 31,591 Items, Two Replicas
8080
[cols="2,3,3"]
@@ -147,9 +147,25 @@ Note that since multiple buckets may have been configured, and different replica
147147

148148
For further examples of rebalance, in the context of _failover_, see xref:learn:clusters-and-availability/failover.adoc[Failover].
149149

150+
=== Changing the IP address of a node
151+
152+
If you are changing the IP address of a node:
153+
154+
. Remove the node from the cluster.
155+
. Stop the server.
156+
. Change the IP address of the node.
157+
. Remove all the configuration files for the cluster affected by the IP change. The configuration files are located in `/opt/couchbase`. To delete the files, run the terminal command:
158+
+
159+
[source, shell]
160+
----
161+
rm -r /opt/couchbase
162+
----
163+
+
164+
. Restart the server.
165+
150166
[#removal-versus-graceful-failover]
151167
== Removal versus Graceful Failover
152168

153169
As an alternative to removal, a responsive Data Service node can be taken out of a cluster by means of _Graceful Failover_.
154-
This may be faster, but the consequences do not maintain previous availability-levels.
170+
This may be faster, but the consequences do not maintain previous availability levels.
155171
An account of the advantages and disadvantages is provided in xref:learn:clusters-and-availability/graceful-failover.adoc#advantages-and-disadvantages[Graceful Failover].

0 commit comments

Comments
 (0)