Search: Do something different with many shard failures #103708
Labels
>bug
priority:normal
A label for assessing bug priority to be used by ES engineers
:Search Foundations/Search
Catch all for Search Foundations
Team:Search
Meta label for search team
Elasticsearch Version
all
Installed Plugins
No response
Java Version
bundled
OS Version
all
Problem Description
I'm looking at a cascading failure caused by the loss of a node hosting many, many, many frozen shards. Coodinating nodes receive a ~6kb shard failure per shard. If you have tens of thousands of shards failing on search request those failure can really add up to some serious memory usage. Maybe we should truncate these?
Steps to Reproduce
See above.
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: