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

Document that data stream write indices cannot be closed

This commit is contained in:
Dan Hermann 2020-06-17 10:39:58 -05:00 committed by GitHub
parent a96f526de1
commit 4962a91157
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/indices/open-close.asciidoc
View File

@ -52,9 +52,15 @@ Identifying indices via wildcards or `_all` can be disabled by setting the
`action.destructive_requires_name` flag in the config file to `true`. `action.destructive_requires_name` flag in the config file to `true`.
This setting can also be changed via the cluster update settings api. This setting can also be changed via the cluster update settings api.
Closed indices consume a significant amount of disk-space which can cause problems in managed environments. Closing indices can be disabled via the cluster settings Closed indices consume a significant amount of disk-space which can cause
problems in managed environments. Closing indices can be disabled via the cluster settings
API by setting `cluster.indices.close.enable` to `false`. The default is `true`. API by setting `cluster.indices.close.enable` to `false`. The default is `true`.
The current write index on a data stream cannot be closed. In order to close
the current write index, the data stream must first be
<<rollover-data-stream-ex,rolled over>> so that a new write index is created
and then the previous write index can be closed.
===== Wait For active shards ===== Wait For active shards
Because opening or closing an index allocates its shards, the Because opening or closing an index allocates its shards, the