We are using 7.3 ES. Due to few bad queries fired by end user, ES CPU/Memory jumps to very high and impacts all others. We want to know any way to stop those long-running queries and return 429 or some status, so the client can handle this.
We got default_search_timeout option which is shard level timeout. And also this results in sending partial data to client. We are looking for some global end user query level settings. Also as I said, we want to return error rather partial data.
Please help us on some options to protect our cluster with these.