Fix pending deletes timeout log message #75776
Merged
Conversation
This file contains hidden or 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
In 2f0d158 we introduced a message reporting a timeout of 30 seconds when acquiring shard locks in order to delete an index, but in fact the timeout is 30 minutes. This commit fixes the message.
DaveCTurner
added
>bug
:Data Management/Indices APIs
elasticmachine
added
the
Team:Data Management
|
Pinging @elastic/es-core-features (Team:Core/Features) |
pugnascotia
approved these changes
Jul 28, 2021
DaveCTurner
added a commit
that referenced
this pull request
Aug 2, 2021
In 2f0d158 we introduced a message reporting a timeout of 30 seconds when acquiring shard locks in order to delete an index, but in fact the timeout is 30 minutes. This commit fixes the message.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In 2f0d158 we introduced a message reporting a timeout of 30
seconds when acquiring shard locks in order to delete an index, but in
fact the timeout is 30 minutes. This commit fixes the message.