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
/// it contains "a list of cluster-manager-eligible nodes used to bootstrap the cluster."
329
+
/// This setting is required on nodes with the cluster-manager node role on a multi-node
330
+
/// cluster. Otherwise the bootstrapping of the cluster fails and all pods report:
331
+
/// > Wait for clusterto be available ...
321
332
///
322
-
/// However, the documentation for Elasticsearch is more detailed and contains the following
323
-
/// notes (see <https://www.elastic.co/guide/en/elasticsearch/reference/9.0/modules-discovery-settings.html>):
333
+
/// This setting must not be set on a single-node cluster, because otherwise the following
334
+
/// error is thrown:
335
+
/// > setting [cluster.initial_cluster_manager_nodes] is not allowed when [discovery.type] is set to [single-node]
336
+
///
337
+
/// see <https://github.com/opensearch-project/OpenSearch/blob/3.1.0/server/src/main/java/org/opensearch/cluster/coordination/ClusterBootstrapService.java#L126-L136>
338
+
///
339
+
/// This setting does not seem to have an effect on nodes without the cluster-manager node
340
+
/// role. However, as it is recommended (see the Elasticsearch documentation below) to not set
341
+
/// it on master-ineligible nodes, it is not set.
342
+
///
343
+
/// This setting seems to be ignored when the cluster has already formed. It is recommended in
344
+
/// the Elasticsearch documentation to remove it once the cluster has formed, but as it is hard
345
+
/// to determine if the bootstrapping was successfully completed, this setting is still set.
346
+
/// Adding a new cluster-manager node and updating this setting also seems to be okay.
347
+
///
348
+
/// # OpenSearch documentation
349
+
///
350
+
/// > This setting is required when bootstrapping a cluster for the first time and should
351
+
/// > contain the node names (as defined by `node.name`) of the initial cluster-manager-eligible
352
+
/// > nodes. This list should be empty for nodes joining an existing cluster.
353
+
///
354
+
/// see <https://docs.opensearch.org/3.3/install-and-configure/configuring-opensearch/discovery-gateway-settings/#static-discovery-settings>
355
+
///
356
+
/// # Elasticsearch documentation
357
+
///
358
+
/// The documentation for Elasticsearch is more detailed and contains the following
359
+
/// notes:
324
360
/// * Remove this setting once the cluster has formed, and never set it again for this cluster.
325
361
/// * Do not configure this setting on master-ineligible nodes.
326
362
/// * Do not configure this setting on nodes joining an existing cluster.
327
363
/// * Do not configure this setting on nodes which are restarting.
328
364
/// * Do not configure this setting when performing a full-cluster restart.
329
365
///
330
-
/// The OpenSearch Helm chart only sets master nodes but does not handle the other cases (see
0 commit comments