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: docs/cluster-formation.md
+26-4Lines changed: 26 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,10 +124,16 @@ so nodes don't have to (or cannot) explicitly register. However, the list of clu
124
124
is not predefined. Such backends usually include a no-op registration step
125
125
and apply one of the [race condition mitigation mechanisms](#initial-formation-race-condition) described below.
126
126
127
-
When the configured backend supports registration, nodes unregister when they stop. It is
128
-
possible to opt-out of registration with the config option `cluster_formation.registration = false`.
129
-
In such cases, the node has to be registered manually or using another mechanism, e.g. with container
130
-
orchestrators like Nomad or Kubernetes.
127
+
If the configured backend supports registration, nodes unregister when they are instructed to stop.
128
+
129
+
It is possible to opt-out of registration completely with the config option `cluster_formation.registration.enabled`:
130
+
131
+
```ini
132
+
cluster_formation.registration.enabled = false
133
+
```
134
+
135
+
When configured this way, the node has to be registered manually or using another mechanism,
136
+
e.g. by a container orchestrator such as [Nomad](https://developer.hashicorp.com/nomad/integrations/hashicorp/rabbitmq) or [Kubernetes](https://www.rabbitmq.com/kubernetes/operator/operator-overview).
131
137
132
138
If peer discovery isn't configured, or it [repeatedly fails](#discovery-retries),
133
139
or no peers are reachable, a node that wasn't a cluster member in the past
Copy file name to clipboardExpand all lines: versioned_docs/version-4.0/cluster-formation.md
+26-1Lines changed: 26 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,16 @@ so nodes don't have to (or cannot) explicitly register. However, the list of clu
124
124
is not predefined. Such backends usually include a no-op registration step
125
125
and apply one of the [race condition mitigation mechanisms](#initial-formation-race-condition) described below.
126
126
127
-
When the configured backend supports registration, nodes unregister when they stop.
127
+
If the configured backend supports registration, nodes unregister when they are instructed to stop.
128
+
129
+
It is possible to opt-out of registration completely with the config option `cluster_formation.registration.enabled`:
130
+
131
+
```ini
132
+
cluster_formation.registration.enabled = false
133
+
```
134
+
135
+
When configured this way, the node has to be registered manually or using another mechanism,
136
+
e.g. by a container orchestrator such as [Nomad](https://developer.hashicorp.com/nomad/integrations/hashicorp/rabbitmq) or [Kubernetes](https://www.rabbitmq.com/kubernetes/operator/operator-overview).
128
137
129
138
If peer discovery isn't configured, or it [repeatedly fails](#discovery-retries),
130
139
or no peers are reachable, a node that wasn't a cluster member in the past
0 commit comments