From 737987439f6978d31148daa611f4b7839c52ca80 Mon Sep 17 00:00:00 2001 From: Ray Offiah Date: Wed, 25 Feb 2026 11:02:25 +0000 Subject: [PATCH 1/3] [DOC-12926]: Feedback on Nodes | Couchbase Docs Added note about changing IP address on node. Minor grammar fixes. Signed-off-by: Ray Offiah --- .../pages/clusters-and-availability/removal.adoc | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/modules/learn/pages/clusters-and-availability/removal.adoc b/modules/learn/pages/clusters-and-availability/removal.adoc index eb0d338d89..9dad9df6d2 100644 --- a/modules/learn/pages/clusters-and-availability/removal.adoc +++ b/modules/learn/pages/clusters-and-availability/removal.adoc @@ -14,7 +14,7 @@ However, removal should be used only when all nodes in the cluster are responsiv Removal essentially means using xref:learn:clusters-and-availability/rebalance.adoc[Rebalance] to redistribute data across a subset of pre-existing cluster-nodes. It can be performed with the UI, the CLI, or the REST API. When the CLI or REST API is used, a single command initiates a rebalance, specifying which nodes are to be excluded. -When the UI is used, nodes to be removed are first identified, then rebalance is initiated. +When the UI is used, nodes to be removed are first identified; then rebalance is initiated. When the rebalance is complete, the _cluster map_ is correspondingly updated and distributed to clients. The process occurs while the cluster continues to service requests for data. @@ -74,7 +74,7 @@ As Table 1 shows, each of the four nodes takes a roughly equal share of the buck It also takes a roughly equal share of the replica bucket-items, kept in _replica_ vBuckets. 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_. -Table 2 shows the results on the cluster of the removal of node 4 and subsequent rebalance. +Table 2 shows the results on the cluster when node 4 is removed and the cluster is rebalanced. .Three Surviving Data Service Nodes, One Bucket with 31,591 Items, Two Replicas [cols="2,3,3"] @@ -147,9 +147,19 @@ Note that since multiple buckets may have been configured, and different replica For further examples of rebalance, in the context of _failover_, see xref:learn:clusters-and-availability/failover.adoc[Failover]. +=== Changing the IP address of a node + +If you are changing the IP address of a node: + +. Remove the node from the cluster. +. Stop the server. +. Remove all the configuration files for the cluster affected by the IP change. +. Restart the server. +. Add the node with the changed IP address back into the cluster. + [#removal-versus-graceful-failover] == Removal versus Graceful Failover As an alternative to removal, a responsive Data Service node can be taken out of a cluster by means of _Graceful Failover_. -This may be faster, but the consequences do not maintain previous availability-levels. +This may be faster, but the consequences do not maintain previous availability levels. An account of the advantages and disadvantages is provided in xref:learn:clusters-and-availability/graceful-failover.adoc#advantages-and-disadvantages[Graceful Failover]. From a8c8f69e8d7bed03c985a28dfdb18162f801643d Mon Sep 17 00:00:00 2001 From: Ray Offiah Date: Fri, 27 Feb 2026 10:15:37 +0000 Subject: [PATCH 2/3] [DOC-12926]: Feedback on Nodes | Couchbase Docs Added instructions for clearing the configuration files. Signed-off-by: Ray Offiah --- .../learn/pages/clusters-and-availability/removal.adoc | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/modules/learn/pages/clusters-and-availability/removal.adoc b/modules/learn/pages/clusters-and-availability/removal.adoc index 9dad9df6d2..8e9419978c 100644 --- a/modules/learn/pages/clusters-and-availability/removal.adoc +++ b/modules/learn/pages/clusters-and-availability/removal.adoc @@ -153,7 +153,13 @@ If you are changing the IP address of a node: . Remove the node from the cluster. . Stop the server. -. Remove all the configuration files for the cluster affected by the IP change. +. 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: ++ +[source, shell] +---- +rm -r /opt/couchbase +---- + . Restart the server. . Add the node with the changed IP address back into the cluster. From 1f891c4bc02bc27e940414869556e128d47b4f00 Mon Sep 17 00:00:00 2001 From: Ray Offiah Date: Fri, 6 Mar 2026 10:22:52 +0000 Subject: [PATCH 3/3] [DOC-12926]: Feedback on Nodes | Couchbase Docs Fixed new instructions. The IP address should be changed while the node is offline. Signed-off-by: Ray Offiah --- modules/learn/pages/clusters-and-availability/removal.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/learn/pages/clusters-and-availability/removal.adoc b/modules/learn/pages/clusters-and-availability/removal.adoc index 8e9419978c..9247f420e2 100644 --- a/modules/learn/pages/clusters-and-availability/removal.adoc +++ b/modules/learn/pages/clusters-and-availability/removal.adoc @@ -153,15 +153,15 @@ If you are changing the IP address of a node: . Remove the node from the cluster. . Stop the server. +. Change the IP address of the node. . 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: + [source, shell] ---- rm -r /opt/couchbase ---- - ++ . Restart the server. -. Add the node with the changed IP address back into the cluster. [#removal-versus-graceful-failover] == Removal versus Graceful Failover