-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create specific exception for when snapshots are in progress #37550
Conversation
Pinging @elastic/es-distributed |
6ffff88
to
f70c0b6
Compare
delete and close index actions threw IllegalArgumentExceptions when attempting to run against an index that has a snapshot in progress. This change introduces a dedicated SnapshotInProgressException for these scenarios. This is done to explicitely signal to clients that this is the reason the action failed, and it is a retryable error. relates to elastic#37541.
f70c0b6
to
f713336
Compare
run gradle build tests 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM but should have @original-brownbear take a look before merging.
run gradle build tests 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (assuming CI goes green eventually), one question/NIT :)
server/src/main/java/org/elasticsearch/snapshots/SnapshotInProgressException.java
Outdated
Show resolved
Hide resolved
thanks for the reviews @dakrone and @original-brownbear! |
run gradle build tests 2 |
…-response-header-performance * elastic/master: Remove Redundant RestoreRequest Class (elastic#37535) Create specific exception for when snapshots are in progress (elastic#37550) Mute UnicastZenPingTests#testSimplePings [DOCS] Adds size limitation to the get datafeeds APIs (elastic#37578) Fix assertion at end of forceRefreshes (elastic#37559) Propagate Errors in executors to uncaught exception handler (elastic#36137) [DOCS] Adds limitation to the get jobs API (elastic#37549) Add set_priority action to ILM (elastic#37397) Make recovery source send operations non-blocking (elastic#37503) Allow field types to optimize phrase prefix queries (elastic#37436) Added fatal_exception field for ccr stats in monitoring mapping. (elastic#37563) Fix testRelocateWhileContinuouslyIndexingAndWaitingForRefresh (elastic#37560) Moved ccr integration to the package with other ccr integration tests. Mute TransportClientNodesServiceTests#testListenerFailures Decreased time out in test Fix erroneous docstrings for abstract bulk by scroll request (elastic#37517) SQL: Rename SQL type DATE to DATETIME (elastic#37395) Remove the AbstracLifecycleComponent constructor with Settings (elastic#37523)
@talevy we intend to delete |
@DaveCTurner I see that change. the plan sounds reasonable to me. I will wait for this change to go in before backporting |
…#37550) delete and close index actions threw IllegalArgumentExceptions when attempting to run against an index that has a snapshot in progress. This change introduces a dedicated SnapshotInProgressException for these scenarios. This is done to explicitly signal to clients that this is the reason the action failed, and it is a retryable error. relates to elastic#37541.
…#37723) delete and close index actions threw IllegalArgumentExceptions when attempting to run against an index that has a snapshot in progress. This change introduces a dedicated SnapshotInProgressException for these scenarios. This is done to explicitly signal to clients that this is the reason the action failed, and it is a retryable error. relates to #37541.
@talevy looks like this was backported now, but does the version need adjusting in the deserialiser? elasticsearch/server/src/main/java/org/elasticsearch/ElasticsearchException.java Line 1013 in 170d741
I'm also wondering whether we're missing a test somewhere, as I would have expected the mixed-cluster tests to pick this up. |
@DaveCTurner thanks for reminding me, I made a note to follow-up on this, but forgot. I noticed |
delete and close index actions threw IllegalArgumentExceptions when
attempting to run against an index that has a snapshot in progress.
This change introduces a dedicated SnapshotInProgressException for
these scenarios. This is done to explicitly signal to clients that
this is the reason the action failed, and it is a retryable error.
relates to #37541.