# Why is the client node resource hungry? **URL:** \ **Category:** Elasticsearch\ **Created:** [April 7, 2017, 7:50pm UTC](https://discuss.elastic.co/t/why-is-the-client-node-resource-hungry/81661 "2017-04-07T19:50:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\ **Post date:** [April 7, 2017, 7:50pm UTC](https://discuss.elastic.co/t/why-is-the-client-node-resource-hungry/81661/1 "2017-04-07T19:50:45Z")
I set up my client node with 16 cores and 64G memory, and set Elasticsearch to use 50% of the memory. Why does it use a lot of CPU and heap? I point my Kibana and Logstash services to the client node. This screen shot is from the kopf plugin. The client node is the fourth from the top. ![](https://us1.discourse-cdn.com/elastic/original/3X/6/3/63754d9bcdd791583f6cb1a73556ecacea89da60.png) ---
**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:** [April 8, 2017, 11:03pm UTC](https://discuss.elastic.co/t/why-is-the-client-node-resource-hungry/81661/2 "2017-04-08T23:03:00Z")
[https://www.elastic.co/guide/en/elasticsearch/guide/current/distributed-search.html](https://www.elastic.co/guide/en/elasticsearch/guide/current/distributed-search.html) explains it. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 6, 2017, 11:04pm UTC](https://discuss.elastic.co/t/why-is-the-client-node-resource-hungry/81661/3 "2017-05-06T23:04:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.