# Coordination Node Client request stats **URL:** \ **Category:** Elasticsearch\ **Created:** [May 12, 2021, 12:48pm UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807 "2021-05-12T12:48:37Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mani1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mani1/32/91044_2.png) [@mani1](https://discuss.elastic.co/u/mani1)\ **Post date:** [May 12, 2021, 12:48pm UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807/1 "2021-05-12T12:48:37Z")
Hi, In our Elasticsearch cluster, there are three coordinatin nodes (dedicated) which are forwarding client search requests to Hot Nodes. There is no load balancer before Coord Nodes. They are receiving client request directly from application. I want to find out which Coord Node is receving how much Client search requests, so that the client search request load distribution among them can be monitored. In node/stats, I am not able to find out the parameter, which is logging this. ---
**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:** [May 12, 2021, 11:16pm UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807/2 "2021-05-12T23:16:43Z")
The Monitoring functionality will show you this. ---
**Author:** ![mani1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mani1/32/91044_2.png) [@mani1](https://discuss.elastic.co/u/mani1)\ **Post date:** [May 13, 2021, 5:39am UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807/3 "2021-05-13T05:39:45Z")
Tx, Which parameter in Kibana's Node monitoring. If it is System Load, which is showing some variation , but it'll will contain indexing request load also alongwith client search request. If, Request rate , but it shows the amount of search operation which is not the case. It will be helpful if some specific monitoring matrix can be suggested. Or any other method ? ---
**Author:** ![mani1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mani1/32/91044_2.png) [@mani1](https://discuss.elastic.co/u/mani1)\ **Post date:** [May 13, 2021, 5:44am UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807/4 "2021-05-13T05:44:10Z")
Also , How to achieve the equal load distribution among all coord Nodes. Do I need to use any seperate load balancer before Coord Nodes. ---
**Author:** ![mani1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mani1/32/91044_2.png) [@mani1](https://discuss.elastic.co/u/mani1)\ **Post date:** [May 17, 2021, 7:10am UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807/5 "2021-05-17T07:10:59Z")
Kindly respond ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 17, 2021, 7:21am UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807/6 "2021-05-17T07:21:24Z")
Why do you need to achieve even load across the nodes? In a highly available setup a subset of the nodes need to be able to handle the full load in case one of the nodes were to go down. Having a load balancer in front of the nodes may help as I am not sure if there is a pattern to how the clients establish connections. Also be aware that most clients establish long-running persistent connections for efficiency, so may not rebalance very quickly. Limiting the lifetime of a connection may help address this but you do not want to establish a connection per request due to the overhead. How to do this will depend on the client(s) used. ---
**Author:** ![munish45](https://avatars.discourse-cdn.com/v4/letter/m/6a8cbe/32.png) [@munish45](https://discuss.elastic.co/u/munish45)\ **Post date:** [May 25, 2021, 2:25pm UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807/7 "2021-05-25T14:25:32Z")
Sometimes the uneven load on EC nodes may overwhelm a particular EC node resulting in heap utilization reaching 100% and making that node non-responsive. Under these conditions, the queries to this node and response will be lost. How the client API sending the queries to all EC nodes will know this status and how the redundancy or failover will be achived. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 22, 2021, 2:25pm UTC](https://discuss.elastic.co/t/coordination-node-client-request-stats/272807/8 "2021-06-22T14:25:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.