# Uneven load on cluster behind ELB with RestClient

**URL:** <https://discuss.elastic.co/t/uneven-load-on-cluster-behind-elb-with-restclient/118179>\
**Category:** Elasticsearch\
**Created:** [February 2, 2018, 8:11am UTC](https://discuss.elastic.co/t/uneven-load-on-cluster-behind-elb-with-restclient/118179 "2018-02-02T08:11:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eduard\_Dudar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eduard_dudar/32/2845_2.png) [@Eduard\_Dudar](https://discuss.elastic.co/u/Eduard_Dudar)\
**Post date:** [February 2, 2018, 8:11am UTC](https://discuss.elastic.co/t/uneven-load-on-cluster-behind-elb-with-restclient/118179/1 "2018-02-02T08:11:12Z")

</div>

Hello,

We've recently migrated from 1.7 to 5.6 and from Jest REST client to High-level REST Client. Our setup is 3 master nodes, 3 client nodes behind ELB and 6 data nodes in 3 availability zones in AWS. When an application starts the load is distributed evenly across 3 client nodes and 6 data nodes. But after some short period of time (10-20 minutes) I notice that client and data nodes are not loaded evenly anymore. Usually, one availability zone takes 80-85% of the load that causes two data nodes to be overloaded while 4 others do mostly nothing. Do restart, again everything is fine for some time then disbalance starts all over again. I checked java dns cache (60s) and outgoing connections from servers (there are conns for each of elb servers).

![11%20AM](https://us1.discourse-cdn.com/elastic/original/3X/a/e/aeb1709333abecfda34e2faefe77b1c8774ec362.png)

Has someone seen such behavior? Any ideas?

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 2, 2018, 8:11am UTC](https://discuss.elastic.co/t/uneven-load-on-cluster-behind-elb-with-restclient/118179/2 "2018-03-02T08:11:18Z")

</div>

Closed on March 2, 2018, 8:11am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
