mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-03 09:29:11 +00:00
c32e4fb83f
In real deployments it is important that clusters are properly configured to avoid accidentally forming multiple independent clusters at cluster bootstrapping time. However we also expect to be able to unpack Elasticsearch and start up one or more nodes without any up-front configuration, and have them do their best to find each other and form a cluster after a few seconds. This change adds a delayed automatic bootstrapping process to nodes that start up with no relevant settings set to support the desired out-of-the-box experience without compromising safety in properly-configured deployments.
37 lines
1.4 KiB
Plaintext
37 lines
1.4 KiB
Plaintext
[float]
|
|
[[breaking_70_cluster_changes]]
|
|
=== Cluster changes
|
|
|
|
[float]
|
|
==== `:` is no longer allowed in cluster name
|
|
|
|
Due to cross-cluster search using `:` to separate a cluster and index name,
|
|
cluster names may no longer contain `:`.
|
|
|
|
[float]
|
|
==== New default for `wait_for_active_shards` parameter of the open index command
|
|
|
|
The default value for the `wait_for_active_shards` parameter of the open index API
|
|
is changed from 0 to 1, which means that the command will now by default wait for all
|
|
primary shards of the opened index to be allocated.
|
|
|
|
[float]
|
|
==== Shard preferences `_primary`, `_primary_first`, `_replica`, and `_replica_first` are removed
|
|
These shard preferences are removed in favour of the `_prefer_nodes` and `_only_nodes` preferences.
|
|
|
|
[float]
|
|
==== Cluster-wide shard soft limit
|
|
Clusters now have soft limits on the total number of open shards in the cluster
|
|
based on the number of nodes and the `cluster.max_shards_per_node` cluster
|
|
setting, to prevent accidental operations that would destabilize the cluster.
|
|
More information can be found in the <<misc-cluster,documentation for that setting>>.
|
|
|
|
[float]
|
|
==== Discovery configuration is required in production
|
|
Production deployments of Elasticsearch now require at least one of the following settings
|
|
to be specified in the `elasticsearch.yml` configuration file:
|
|
|
|
- `discovery.zen.ping.unicast.hosts`
|
|
- `discovery.zen.hosts_provider`
|
|
- `cluster.initial_master_nodes`
|