# Opinions on using different client nodes for indexing and searching

**URL:** <https://discuss.elastic.co/t/opinions-on-using-different-client-nodes-for-indexing-and-searching/45913>\
**Category:** Elasticsearch\
**Created:** [March 31, 2016, 10:23am UTC](https://discuss.elastic.co/t/opinions-on-using-different-client-nodes-for-indexing-and-searching/45913 "2016-03-31T10:23:26Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![lwintergerst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lwintergerst/32/18164_2.png) [@lwintergerst](https://discuss.elastic.co/u/lwintergerst)\
**Post date:** [April 28, 2016, 5:41am UTC](https://discuss.elastic.co/t/opinions-on-using-different-client-nodes-for-indexing-and-searching/45913/5 "2016-04-28T05:41:43Z")

</div>

Here you go

> [@Find out what causes long GC cycles on client node](https://discuss.elastic.co/t/find-out-what-causes-long-gc-cycles-on-client-node/45917/2):
>
> This might be useful references: For me, it was almost always fielddata. Look for evictions in that and filterdata. \_node/stats and/or marvel or other monitor is your friend for troubleshooting this. If you are not using doc\_values, it can help (at some indexing cost).

---

_[View the full topic](https://discuss.elastic.co/t/opinions-on-using-different-client-nodes-for-indexing-and-searching/45913)._