Skip to content

Commit bee43b9

Browse files
gbanasiakjrodewig
andauthored
[DOCS] Clarify atomic change for alias swaps (elastic#59154)
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]>
1 parent 38667b8 commit bee43b9

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/reference/indices/aliases.asciidoc

+4-2
Original file line numberDiff line numberDiff line change
@@ -263,8 +263,10 @@ indices that match this pattern are added/removed.
263263
It is an error to index to an alias which points to more than one index.
264264

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

269271
[source,console]
270272
--------------------------------------------------

0 commit comments

Comments
 (0)