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

Document the prohibition on freezing data stream write indices (#58058) (#58705)

This commit is contained in:
Dan Hermann 2020-06-29 16:34:36 -05:00 committed by GitHub
parent 35a703db16
commit 84513c7539
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/reference/indices/apis/freeze.asciidoc
View File

@ -6,7 +6,7 @@
<titleabbrev>Freeze index</titleabbrev> <titleabbrev>Freeze index</titleabbrev>
++++ ++++
Freezes an index. Freezes an index.
[[freeze-index-api-request]] [[freeze-index-api-request]]
==== {api-request-title} ==== {api-request-title}
@ -24,6 +24,11 @@ metadata in memory) and is read-only. Read-only indices are blocked for write
operations, such as <<indexing,docs-index_>> or <<indices-forcemerge,force operations, such as <<indexing,docs-index_>> or <<indices-forcemerge,force
merges>>. See <<frozen-indices>> and <<unfreeze-index-api>>. merges>>. See <<frozen-indices>> and <<unfreeze-index-api>>.
The current write index on a data stream cannot be frozen. In order to freeze
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 frozen.
IMPORTANT: Freezing an index will close the index and reopen it within the same IMPORTANT: Freezing an index will close the index and reopen it within the same
API call. This causes primaries to not be allocated for a short amount of time API call. This causes primaries to not be allocated for a short amount of time
and causes the cluster to go red until the primaries are allocated again. This and causes the cluster to go red until the primaries are allocated again. This