# Need help to configure cluster for heavy index **URL:** \ **Category:** Elasticsearch\ **Created:** [July 2, 2015, 9:08am UTC](https://discuss.elastic.co/t/need-help-to-configure-cluster-for-heavy-index/24775 "2015-07-02T09:08:35Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![limac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/limac/32/3981_2.png) [@limac](https://discuss.elastic.co/u/limac)\ **Post date:** [July 2, 2015, 9:08am UTC](https://discuss.elastic.co/t/need-help-to-configure-cluster-for-heavy-index/24775/1 "2015-07-02T09:08:35Z")
hi there, I have a cluster with 4 data nodes, 2 master only nodes, and 1 client node. The index load is pretty much high, about 10k/s, with about 200 query requests per second. So, route all index and query requests to client node, or route all index requests to data nodes directly and query request to client node, which one is a better choice and what is the different? Many thanks! Alan ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 2, 2015, 11:57pm UTC](https://discuss.elastic.co/t/need-help-to-configure-cluster-for-heavy-index/24775/2 "2015-07-02T23:57:28Z")
I'd send queries to the client node and indexing to the data nodes. You also probably want to have 3 master nodes to help prevent split-brain. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:03am UTC](https://discuss.elastic.co/t/need-help-to-configure-cluster-for-heavy-index/24775/3 "2017-07-06T00:03:51Z")