-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Stricter failure handling in
TransportGetSnapshotsAction
(#107191)
Today if there's a failure during a multi-repo get-snapshots request then we record a per-repository failure but allow the rest of the request to proceed. This is trappy for clients, it means that they must always remember to check the `failures` response field or else risk missing some results. It's also a pain for the implementation because it means we have to collect the per-repository results separately first before adding them to the final results set just in case the last one triggers a failure. This commit drops this leniency and bubbles all failures straight up to the top level.
- Loading branch information
1 parent
69ee6d7
commit c5e8173
Showing
6 changed files
with
47 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
pr: 107191 | ||
summary: Stricter failure handling in multi-repo get-snapshots request handling | ||
area: Snapshot/Restore | ||
type: bug | ||
issues: [] | ||
highlight: | ||
title: Stricter failure handling in multi-repo get-snapshots request handling | ||
body: | | ||
If a multi-repo get-snapshots request encounters a failure in one of the | ||
targeted repositories then earlier versions of Elasticsearch would proceed | ||
as if the faulty repository did not exist, except for a per-repository | ||
failure report in a separate section of the response body. This makes it | ||
impossible to paginate the results properly in the presence of failures. In | ||
versions 8.15.0 and later this API's failure handling behaviour has been | ||
made stricter, reporting an overall failure if any targeted repository's | ||
contents cannot be listed. | ||
notable: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters