It should not be possible to cause a shard to fail just by sending it too much indexing traffic. Instead, ES should just push back (typically by returning a 429 Too Many Requests). So if it's not doing that for some reason then we need to understand why and address the fundamental problem. For instance, what is the exact nature of the shard failure? What appears in the ES logs, for instance, and in the responses to indexing requests? Perhaps this is a bug, but we cannot fix it without understanding it in more detail.
1 Like