Shard indexing backpressure

With shard indexing backpressure, you can prevent nodes in your cluster from running into cascading failures due to performance degradation caused by slow nodes, stuck tasks, resource-intensive requests, traffic surges, skewed shard allocations, and so on.

Primary parameters are early indicators that a cluster is under strain:

• Shard memory limit breach: If the memory usage of a shard exceeds 95% of its allocated memory, this limit is breached.
• Node memory limit breach: If the memory usage of a node exceeds 70% of its allocated memory, this limit is breached.

Secondary parameters check the performance at the shard level to confirm that the cluster is under strain:

• Successful Request: If the number of pending requests increases significantly in its historic view, this limit is breached.