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

Update misc.asciidoc 

Added documentation for the cluster.indices.tombstones.size property for maximum tombstones in the cluster state.
This commit is contained in:
Ali Beyad 2016-05-04 15:21:47 -04:00
parent 124e8e5a6d
commit 67c0734bf3
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -17,6 +17,23 @@ user with access to the <<cluster-update-settings,cluster-update-settings>>
API can make the cluster read-write again. API can make the cluster read-write again.
[[cluster-max-tombstones]]
==== Index Tombstones
The cluster state maintains index tombstones to explicitly denote indices that
have been deleted. The number of tombstones maintained in the cluster state is
controlled by the following property, which cannot be updated dynamically:
`cluster.indices.tombstones.size`::
Index tombstones prevent nodes that are not part of the cluster when a delete
occurs from joining the cluster and reimporting the index as though the delete
was never issued. To keep the cluster state from growing huge we only keep the
last `cluster.indices.tombstones.size` deletes, which defaults to 500. You can
increase it if you expect nodes to be absent from the cluster and miss more
than 500 deletes. We think that is rare, thus the default. Tombstones don't take
up much space, but we also think that a number like 50,000 is probably too big.
[[cluster-logger]] [[cluster-logger]]
==== Logger ==== Logger