# Distributed Requests from Rally

**URL:** <https://discuss.elastic.co/t/distributed-requests-from-rally/177361>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [April 17, 2019, 6:41pm UTC](https://discuss.elastic.co/t/distributed-requests-from-rally/177361 "2019-04-17T18:41:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rocksnslopes](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rocksnslopes](https://discuss.elastic.co/u/rocksnslopes)\
**Post date:** [April 17, 2019, 6:41pm UTC](https://discuss.elastic.co/t/distributed-requests-from-rally/177361/1 "2019-04-17T18:41:52Z")

</div>

Hi -

I have slightly modified the percolator challenge to something like this:

...  
"parallel": {  
"tasks": [  
{  
"operation": "percolator\_with\_content\_president\_bush",  
"clients": 100,  
"warmup-iterations": 100,  
"iterations": 100,  
"target-throughput": 10000  
}  
]  
...

At first I run rally through a load balancer with this command:

$ esrally --track-path=percolator/ --report-format=csv --report-file=reports/race.csv --target-hosts=[internal-someelb.us-east-1.elb.amazonaws.com:9200](http://internal-someelb.us-east-1.elb.amazonaws.com:9200) --pipeline=benchmark-only

There are about 12-48 data nodes to a load balancer, but when monitoring the data nodes, I noticed only 1 maybe 2 actually receiving requests from rally. Is this normal? At first I thought maybe my load balancer wasn't configured correctly. Then I decided to by-pass the lb by explicitly listing out each data node in the target-hosts flag. Surprisingly, I received the same result, only 1 or 2 data nodes receive the requests.

Is there a way to configure rally to distribute the requests evenly over all the target hosts or all the nodes via a lb?

---

<div class="post-metadata">

**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:** [April 18, 2019, 4:58am UTC](https://discuss.elastic.co/t/distributed-requests-from-rally/177361/2 "2019-04-18T04:58:14Z")

</div>

Rally will be using long running connections so if you are using a load balancer it will depend on how this routs connections when rally is starting up and connections established. If you provide a long list of ups instead I am not sure any coordination is done between the clients, so would be less surprised if this led to an imbalance. I bet @danielmitterdorfer can clarify though.

---

<div class="post-metadata">

**Author:** ![rocksnslopes](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rocksnslopes](https://discuss.elastic.co/u/rocksnslopes)\
**Post date:** [April 18, 2019, 3:54pm UTC](https://discuss.elastic.co/t/distributed-requests-from-rally/177361/3 "2019-04-18T15:54:58Z")

</div>

Thanks Christian. I think my issue is the default track params. I didn't override with --track-params flag, and my number\_of\_shards was defaulting to 5.

---

<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:** [May 16, 2019, 4:05pm UTC](https://discuss.elastic.co/t/distributed-requests-from-rally/177361/4 "2019-05-16T16:05:20Z")

</div>

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