You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/learn/pages/clusters-and-availability/removal.adoc
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ However, removal should be used only when all nodes in the cluster are responsiv
14
14
Removal essentially means using xref:learn:clusters-and-availability/rebalance.adoc[Rebalance] to redistribute data across a subset of pre-existing cluster-nodes.
15
15
It can be performed with the UI, the CLI, or the REST API.
16
16
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.
18
18
When the rebalance is complete, the _cluster map_ is correspondingly updated and distributed to clients.
19
19
The process occurs while the cluster continues to service requests for data.
20
20
@@ -74,7 +74,7 @@ As Table 1 shows, each of the four nodes takes a roughly equal share of the buck
74
74
It also takes a roughly equal share of the replica bucket-items, kept in _replica_ vBuckets.
75
75
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_.
76
76
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.
78
78
79
79
.Three Surviving Data Service Nodes, One Bucket with 31,591 Items, Two Replicas
80
80
[cols="2,3,3"]
@@ -147,9 +147,25 @@ Note that since multiple buckets may have been configured, and different replica
147
147
148
148
For further examples of rebalance, in the context of _failover_, see xref:learn:clusters-and-availability/failover.adoc[Failover].
149
149
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
+
150
166
[#removal-versus-graceful-failover]
151
167
== Removal versus Graceful Failover
152
168
153
169
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 availabilitylevels.
155
171
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