# Multiple node cluster worse than single node

**URL:** <https://discuss.elastic.co/t/multiple-node-cluster-worse-than-single-node/109308>\
**Category:** Elasticsearch\
**Created:** [November 28, 2017, 5:13am UTC](https://discuss.elastic.co/t/multiple-node-cluster-worse-than-single-node/109308 "2017-11-28T05:13:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zhengcong\_Yin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhengcong_yin/32/62960_2.png) [@Zhengcong\_Yin](https://discuss.elastic.co/u/Zhengcong_Yin)\
**Post date:** [November 28, 2017, 5:13am UTC](https://discuss.elastic.co/t/multiple-node-cluster-worse-than-single-node/109308/1 "2017-11-28T05:13:29Z")

</div>

I had 43G data to do the match query. When I set up a single node (no dedicated role), it works very well. After I set up a cluster, 3 master node, 2 data node and 1 client node. The time took for each query seems like to be double than it took in the single node scenario. Could somebody give me a hint about this situation? Really appreciated!

Thanks!

---

<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:** [December 26, 2017, 5:13am UTC](https://discuss.elastic.co/t/multiple-node-cluster-worse-than-single-node/109308/2 "2017-12-26T05:13:52Z")

</div>

Closed on December 26, 2017, 5:13am UTC

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