mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-06 04:58:50 +00:00
da20dfd81c
In a future major version, we will be introducing a soft limit on the number of shards in a cluster based on the number of nodes in the cluster. This limit will be configurable, and checked on operations which create or open shards and issue a warning if the operation would take the cluster over the limit. There is an option to enable strict enforcement of the limit, which turns the warnings into errors. In a future release, the option will be removed and strict enforcement will be the default (and only) behavior.
27 lines
1.1 KiB
Plaintext
27 lines
1.1 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>>. |