honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

updated shard limit doc (#56496) (#61509) 

* updated shard limit doc

As the documentation was not so clear. I have updated saying this limit includes open indices with unassigned primaries and replicas count towards the limit.

* [DOCS] Incorporated edits.

Co-authored-by: Deb Adair <debadair@elastic.co>

Co-authored-by: gadekishore <50092970+gadekishore@users.noreply.github.com>
This commit is contained in:
debadair 2020-08-25 14:24:47 -07:00 committed by GitHub
parent e0843571c4
commit 82585107aa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/reference/modules/cluster/misc.asciidoc
View File

@ -45,20 +45,20 @@ either the limit is increased as described below, or some indices are
<<indices-open-close,closed>> or <<indices-delete-index,deleted>> to bring the <<indices-open-close,closed>> or <<indices-delete-index,deleted>> to bring the
number of shards below the limit. number of shards below the limit.
Replicas count towards this limit, but closed indexes do not. An index with 5 The cluster shard limit defaults to 1,000 shards per data node.
primary shards and 2 replicas will be counted as 15 shards. Any closed index Both primary and replica shards of all open indices count toward the limit,
is counted as 0, no matter how many shards and replicas it contains. including unassigned shards.
For example, an open index with 5 primary shards and 2 replicas counts as 15 shards.
Closed indices do not contribute to the shard count.
The limit defaults to 1,000 shards per data node, and can be dynamically You can dynamically adjust the cluster shard limit with the following property:
adjusted using the following property:
`cluster.max_shards_per_node`:: `cluster.max_shards_per_node`::
Controls the number of shards allowed in the cluster per data node. Controls the number of shards allowed in the cluster per data node.
For example, a 3-node cluster with the default setting would allow 3,000 shards With the default setting, a 3-node cluster allows 3,000 shards total, across all open indexes.
total, across all open indexes. If the above setting is changed to 500, then If you reduce the limit to 500, the cluster would allow 1,500 shards total.
the cluster would allow 1,500 shards total.
NOTE: If there are no data nodes in the cluster, the limit will not be enforced. NOTE: If there are no data nodes in the cluster, the limit will not be enforced.
This allows the creation of indices during cluster creation if dedicated master This allows the creation of indices during cluster creation if dedicated master