From 84513c7539a398f88ee110c8b35f2ea409ae9b8f Mon Sep 17 00:00:00 2001
From: Dan Hermann <danhermann@users.noreply.github.com>
Date: Mon, 29 Jun 2020 16:34:36 -0500
Subject: [PATCH] Document the prohibition on freezing data stream write
 indices (#58058) (#58705)

---
 docs/reference/indices/apis/freeze.asciidoc | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/reference/indices/apis/freeze.asciidoc b/docs/reference/indices/apis/freeze.asciidoc
index e123e93bd30..9ff7f4f0248 100644
--- a/docs/reference/indices/apis/freeze.asciidoc
+++ b/docs/reference/indices/apis/freeze.asciidoc
@@ -6,7 +6,7 @@
 <titleabbrev>Freeze index</titleabbrev>
 ++++
 
-Freezes an index. 
+Freezes an index.
 
 [[freeze-index-api-request]]
 ==== {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
 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
 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