Skip to content

Commit 66b16ae

Browse files
jrodewiggbanasiak
andauthored
[DOCS] Clarify atomic change for alias swaps (#59154) (#59165)
Small edit highlighting the fact that atomic cluster state change does not guarantee lack of errors for in-flight requests. Co-authored-by: James Rodewig <[email protected]> Co-authored-by: Grzegorz Banasiak <[email protected]>
1 parent fc47e01 commit 66b16ae

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/reference/indices/aliases.asciidoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -259,8 +259,10 @@ indices that match this pattern are added/removed.
259259
It is an error to index to an alias which points to more than one index.
260260

261261
It is also possible to swap an index with an alias in one, atomic operation.
262-
This means there will be no period of downtime where the alias points to no
263-
index.
262+
This means there will be no point in time where the alias points to no
263+
index in the cluster state. However, as indexing and searches involve multiple
264+
steps, it is possible for the in-flight or queued requests to fail
265+
due to a temporarily non-existent index.
264266

265267
[source,console]
266268
--------------------------------------------------

0 commit comments

Comments
 (0)