# How to prevent a single node slowing down queries where it acts as the coordinator?

**URL:** <https://discuss.elastic.co/t/how-to-prevent-a-single-node-slowing-down-queries-where-it-acts-as-the-coordinator/286937>\
**Category:** Elasticsearch\
**Created:** [October 17, 2021, 9:20pm UTC](https://discuss.elastic.co/t/how-to-prevent-a-single-node-slowing-down-queries-where-it-acts-as-the-coordinator/286937 "2021-10-17T21:20:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ted.fed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ted.fed/32/56636_2.png) [@ted.fed](https://discuss.elastic.co/u/ted.fed)\
**Post date:** [October 17, 2021, 9:20pm UTC](https://discuss.elastic.co/t/how-to-prevent-a-single-node-slowing-down-queries-where-it-acts-as-the-coordinator/286937/1 "2021-10-17T21:20:32Z")

</div>

As per my understanding, clients do not have a server-preference for sending read queries and do either a round-robin or a random client selection.  
If so, then each server acts as a coordinator node (one that scatter-gathers).  
And if any one node is slow, then the queries on that slow node have to be slow (About 1/N queries where N is the total number of data nodes in the cluster).  
Is there any way to prevent such a thing?  
For example, Cassandra has [speculative retries](https://docs.datastax.com/en/developer/java-driver/3.2/manual/speculative_execution/) to overcome the same.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 14, 2021, 9:20pm UTC](https://discuss.elastic.co/t/how-to-prevent-a-single-node-slowing-down-queries-where-it-acts-as-the-coordinator/286937/2 "2021-11-14T21:20:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.