Make shard exhaustion events a retry-able error. #148
Conversation
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
When an opensearch cluster is at full shard capacity, we shouldn't send these messages to `@ERROR` as quite often the next practical step would be to free up shards or expand the cluster. This will save users from having to process messages from wherever they send their `@ERROR` output to. Signed-off-by: Darren Oakley <[email protected]>
dazoakley
force-pushed
the
shard-exhaustion
branch
from
49291b0 to
a1ee2b3
Compare
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.
When an opensearch cluster is at full shard capacity, we shouldn't send these messages to
@ERRORas quite often the next practical step would be to free up shards or expand the cluster.This will save users from having to process messages from wherever they send their
@ERRORoutput to.