|
|
@@ -1,7 +1,7 @@
|
|
|
[role="xpack"]
|
|
|
[testenv="basic"]
|
|
|
[[frozen-indices]]
|
|
|
-= Frozen Indices
|
|
|
+= Frozen indices
|
|
|
|
|
|
[partintro]
|
|
|
--
|
|
|
@@ -47,7 +47,10 @@ To make a frozen index writable again, use the <<unfreeze-index-api, Unfreeze In
|
|
|
|
|
|
--
|
|
|
|
|
|
-== Best Practices
|
|
|
+[role="xpack"]
|
|
|
+[testenv="basic"]
|
|
|
+[[best_practices]]
|
|
|
+== Best practices
|
|
|
|
|
|
Since frozen indices provide a much higher disk to heap ratio at the expense of search latency, it is advisable to allocate frozen indices to
|
|
|
dedicated nodes to prevent searches on frozen indices influencing traffic on low latency nodes. There is significant overhead in loading
|
|
|
@@ -66,10 +69,13 @@ POST /twitter/_forcemerge?max_num_segments=1
|
|
|
// CONSOLE
|
|
|
// TEST[setup:twitter]
|
|
|
|
|
|
+[role="xpack"]
|
|
|
+[testenv="basic"]
|
|
|
+[[searching_a_frozen_index]]
|
|
|
== Searching a frozen index
|
|
|
|
|
|
Frozen indices are throttled in order to limit memory consumptions per node. The number of concurrently loaded frozen indices per node is
|
|
|
-limited by the number of threads in the <<search-throttled>> threadpool, which is `1` by default.
|
|
|
+limited by the number of threads in the <<search-throttled,search_throttled>> threadpool, which is `1` by default.
|
|
|
Search requests will not be executed against frozen indices by default, even if a frozen index is named explicitly. This is
|
|
|
to prevent accidental slowdowns by targeting a frozen index by mistake. To include frozen indices a search request must be executed with
|
|
|
the query parameter `ignore_throttled=false`.
|
Lisa Cawley