I am trying to setup esrally in k8s, As per the Tips and Tricks — Rally 2.2.1 documentation it is good approach or solution to distribute the load to loaddrivers. what would be the better configurations for loaddrivers(like cpu,ram). kindly suggest.
Since you intend to use Rally in k8s, I assume you'll be using the Rally Docker image. As mentioned in the docs the Rally Docker image doesn't (currently at least) support distributing the load driver, so it'd be best to ensure that wherever Rally ends up running, limited resources on the load driver are not going to be a cause for bottlenecking your benchmark.
That the Rally container always ends up running on the same underlying host to reduce run to run variation (this is of course more pertinent to the target Elasticsearch itself, but it's good to ensure stable performance on the load driver too) and that the container doesn't end up running on a host that is severely overloaded.
Container and underlying host metrics while the benchmark is running to ensure that the benchmark isn't affected by CPU/Disk IO/Network/Memory bottlenecks.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.