[DOCS] Clarify atomic change for alias swaps (#59154) (#59164)

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 <james.rodewig@elastic.co>

Co-authored-by: Grzegorz Banasiak <grzegorz.banasiak@elastic.co>
This commit is contained in:
James Rodewig 2020-07-07 13:03:12 -04:00 committed by GitHub
parent 93ff5bf9c8
commit 189d69d826
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions

View File

@ -263,8 +263,10 @@ indices that match this pattern are added/removed.
It is an error to index to an alias which points to more than one index.
It is also possible to swap an index with an alias in one, atomic operation.
This means there will be no period of downtime where the alias points to no
index.
This means there will be no point in time where the alias points to no
index in the cluster state. However, as indexing and searches involve multiple
steps, it is possible for the in-flight or queued requests to fail
due to a temporarily non-existent index.
[source,console]
--------------------------------------------------