# Two same nodes but different stats **URL:** \ **Category:** Elasticsearch\ **Created:** [August 3, 2015, 2:49am UTC](https://discuss.elastic.co/t/two-same-nodes-but-different-stats/26696 "2015-08-03T02:49:07Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Eugene\_Strokin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eugene_strokin/32/1238_2.png) [@Eugene\_Strokin](https://discuss.elastic.co/u/Eugene_Strokin)\ **Post date:** [August 3, 2015, 2:49am UTC](https://discuss.elastic.co/t/two-same-nodes-but-different-stats/26696/1 "2015-08-03T02:49:07Z")
Hello, I have a cluster with replica =1. So, I have 2 nodes which serve same shards. BigDesk shows that both of them have similar number "Search requests per second", but "Search time per second" number on the second node is about twice larger. Also CPU consumption is higher on the second node. What could it be? Where could I start troubleshoot the problem? Thanks, Eugene ---
**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:** [August 3, 2015, 2:57am UTC](https://discuss.elastic.co/t/two-same-nodes-but-different-stats/26696/2 "2015-08-03T02:57:45Z")
How are you indexing and searching into the cluster, are you using load balancing? Take a look at hot\_threads and GC as well. ---
**Author:** ![Eugene\_Strokin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eugene_strokin/32/1238_2.png) [@Eugene\_Strokin](https://discuss.elastic.co/u/Eugene_Strokin)\ **Post date:** [August 3, 2015, 3:03am UTC](https://discuss.elastic.co/t/two-same-nodes-but-different-stats/26696/3 "2015-08-03T03:03:37Z")
For indexing and searching I'm using Java API client it connects via transport protocol (port 9300). GC shows about the same numbers as well. I don't use load balancer, the client has all the nodes seeded and sniff property is true. Similar number of requests per second makes me think that the client distributes requests evenly. But "Search time per second" probably says that the second node slower for some reason, even though they are the same hardware, and built from the same image. I ran hot\_threads many times, I don't understand how it could help, I see that search is one of the busiest thread, which I guess is the expected behavior. Here is an example: > Thanks, Eugene ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:57pm UTC](https://discuss.elastic.co/t/two-same-nodes-but-different-stats/26696/4 "2017-07-05T23:57:48Z")