# Benchmarking using ESRally

**URL:** <https://discuss.elastic.co/t/benchmarking-using-esrally/335735>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [June 12, 2023, 6:10am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735 "2023-06-12T06:10:18Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Darshan\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_j/32/119447_2.png) [@Darshan\_J](https://discuss.elastic.co/u/Darshan_J)\
**Post date:** [June 12, 2023, 6:10am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/1 "2023-06-12T06:10:18Z")

</div>

Hey there,  
I'm new to ESRally and I would appreciate some assistance in running esrally with ES running on a remote server.

The set-up:  
There is a remote server which I connect to it via ssh.. it has a single elasticsearch pod running in it. So I have the ip address of the server and even that of pod. The elasticsearch in the pod already has some indices and data in it. Due to some reasons Im not able to install esrally on that server..  
So how can i connect to the server and connect to the pod and run `create-track` command from my local machine so that I can get a custom track and then run some benchmarking on the ES running in a pod. If there are some tutorials or hands-on about this then please point it out I will follow that.

Thank you.

---

<div class="post-metadata">

**Author:** ![Quentin\_Pradet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quentin_pradet/32/94192_2.png) [@Quentin\_Pradet](https://discuss.elastic.co/u/Quentin_Pradet)\
**Post date:** [June 12, 2023, 6:36am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/2 "2023-06-12T06:36:09Z")

</div>

Hello,

Would the offline install ([Installation - Rally 2.7.1 documentation](https://esrally.readthedocs.io/en/stable/install.html#offline-install)) work for you? Or is there a way to copy the data somewhere an install of Rally could reach it?

The last option could be to set up an SSH tunnel ([What is an SSH Tunnel & SSH Tunneling?](https://www.ssh.com/academy/ssh/tunneling)) which I think could work. But we cannot help you directly with that, sorry.

---

<div class="post-metadata">

**Author:** ![Darshan\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_j/32/119447_2.png) [@Darshan\_J](https://discuss.elastic.co/u/Darshan_J)\
**Post date:** [June 12, 2023, 7:04am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/3 "2023-06-12T07:04:29Z")

</div>

> [@Quentin\_Pradet](#):
>
> Installation - Rally 2.7.1 documentation

Thanks @Quentic\_Pradet for the reply.  
So if I install esrally offline on the remote server. Should I have to install esrally in the pods also to carry out benchmarking since the Elasticsearch is running inside pods ?

---

<div class="post-metadata">

**Author:** ![gbanasiak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gbanasiak/32/121454_2.png) [@gbanasiak](https://discuss.elastic.co/u/gbanasiak)\
**Post date:** [June 12, 2023, 10:03am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/4 "2023-06-12T10:03:25Z")

</div>

Hi Dershan,

No, you don't need to install `esrally` inside the pods. You can use `--pipeline=benchmark-only` option to benchmark existing K8s cluster. The only requirement is `esrally` needs to be able to connect to TCP/9200 or any other port where Elasticsearch running in the pod is exposed. See here for more details: [Tips and Tricks - Rally 2.7.1 documentation](https://esrally.readthedocs.io/en/stable/recipes.html?highlight=existing%20cluster#benchmarking-an-existing-cluster) .

Please note testing an existing cluster may affect other traffic in this cluster, so it's not recommended to benchmark a production cluster unless you know what you're doing 🙂

Kind regards.

---

<div class="post-metadata">

**Author:** ![Darshan\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_j/32/119447_2.png) [@Darshan\_J](https://discuss.elastic.co/u/Darshan_J)\
**Post date:** [June 12, 2023, 10:38am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/5 "2023-06-12T10:38:52Z")

</div>

Thanks @gbanasiak for your reply and no I'm not benchmarking a production cluster, its for testing purpose only, thanks for your help 🙂 .

---

<div class="post-metadata">

**Author:** ![Darshan\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_j/32/119447_2.png) [@Darshan\_J](https://discuss.elastic.co/u/Darshan_J)\
**Post date:** [June 14, 2023, 5:09am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/6 "2023-06-14T05:09:44Z")

</div>

Hello,  
I used offline method to install ESrally on a server. In that server I have one Elasticsearch statefulset pod running. I was able to connect to the pod and do any operations using curl commands using the pod ip with 9200 port number. I ran this command `esrally create-track --track=acme --target-hosts=<pod_ip>:9200 --indices="topology-devices-,audit_trail_2023_5" --output-path=~/tracks` with the same pod ip and port number used in curl commands. But Im getting the following error  
`[ERROR] Cannot create-track. The client noticed that the server is not Elasticsearch and we do not support this unknown product.`. I can assure that the ip address belongs to a elasticsearch pod. I'm not sure why it says so... Is it something related to elasticsearch version, should I have to mention it somewhere to rally which version of ES I'm using ? I would really appreciate some assistance in this matter.

---

<div class="post-metadata">

**Author:** ![gbanasiak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gbanasiak/32/121454_2.png) [@gbanasiak](https://discuss.elastic.co/u/gbanasiak)\
**Post date:** [June 14, 2023, 8:34am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/7 "2023-06-14T08:34:57Z")

</div>

Can you share `GET /` response from your cluster retrieved via `curl` including the exact command used? Please add `-i` option to include the headers returned by Elasticsearch.

Example based on Elastic Cloud deployment (hence HTTPS and port 9243):

```auto
% curl -i -u elastic:<password> https://<URL>:9243
HTTP/2 200
content-type: application/json
x-cloud-request-id: <REDACTED>
x-elastic-product: Elasticsearch
x-found-handling-cluster: <REDACTED>
x-found-handling-instance: instance-0000000000
content-length: 564
date: Wed, 14 Jun 2023 08:16:32 GMT

{
  "name" : "instance-0000000000",
  "cluster_name" : "<REDACTED>",
  "cluster_uuid" : "<REDACTED>",
  "version" : {
    "number" : "8.8.0",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : "c01029875a091076ed42cdb3a41c10b1a9a5a20f",
    "build_date" : "2023-05-23T17:16:07.179039820Z",
    "build_snapshot" : false,
    "lucene_version" : "9.6.0",
    "minimum_wire_compatibility_version" : "7.17.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "You Know, for Search"
}

```

Please also share Rally stack trace from `~/.rally/logs/rally.log` corresponding to the error you mentioned. `GET /` response seems to be failing [this](https://github.com/elastic/rally/blob/675f1bdbe1fb96f07fefd947a1cd316525544b3a/esrally/client/synchronous.py#L77) verification but let's double-check.

---

<div class="post-metadata">

**Author:** ![Darshan\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_j/32/119447_2.png) [@Darshan\_J](https://discuss.elastic.co/u/Darshan_J)\
**Post date:** [June 14, 2023, 9:44am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/8 "2023-06-14T09:44:07Z")

</div>

For the command `curl -i <ipaddress>:9200`  
Output:

```auto
content-type: application/json; charset=UTF-8
content-length: 345

{
  "name" : "elasticsearch-1",
  "cluster_name" : "search-es-cluster-main",
  "cluster_uuid" : "OzTzf1q6Q_epkB5Z7hiq7g",
  "version" : {
    "number" : "5.6.16",
    "build_hash" : "3a740d1",
    "build_date" : "2019-03-13T15:33:36.565Z",
    "build_snapshot" : false,
    "lucene_version" : "6.6.1"
  },
  "tagline" : "You Know, for Search"
}

```

I was using curl -X GET /\_cat/indices

```auto
curl -X GET "<ipaddress>:9200/_cat/indices?v=true&pretty" -i

Output:
HTTP/1.1 200 OK
content-type: text/plain; charset=UTF-8
content-length: 21593
<and all indices list>

```

Contents of log file when I ran esrally create-track

```auto
2023-06-14 09:40:17,571 -not-actor-/PID:20774 esrally.rally INFO OS [uname_result(system='Linux', node=' ***-156-248.***.com', release='4.15.0-1039-fips', version='#44+recert2+tpmfix $
2023-06-14 09:40:17,571 -not-actor-/PID:20774 esrally.rally INFO Python [namespace(_multiarch='x86_64-linux-gnu', cache_tag='cpython-38', hexversion=50856176, name='cpython', version=sys.ve$
2023-06-14 09:40:17,571 -not-actor-/PID:20774 esrally.rally INFO Rally version [2.8.0]
2023-06-14 09:40:17,571 -not-actor-/PID:20774 esrally.utils.net INFO Connecting directly to the Internet (no proxy support) for [all_proxy].
2023-06-14 09:40:17,571 -not-actor-/PID:20774 esrally.utils.net INFO Connecting directly to the Internet (no proxy support) for [all_proxy].
2023-06-14 09:40:17,571 -not-actor-/PID:20774 esrally.rally INFO Cleaning track dependency directory [/home/core/.rally/libs]...
2023-06-14 09:40:17,571 -not-actor-/PID:20774 esrally.client.factory INFO Creating ES client connected to [{'host': '<ipaddress>', 'port': 9200}] with options [{'timeout': 60}]
2023-06-14 09:40:17,631 -not-actor-/PID:20774 esrally.rally ERROR A fatal error occurred while running subcommand [create-track].
Traceback (most recent call last):
  File "/home/core/venv/lib/python3.8/site-packages/esrally/rally.py", line 1186, in dispatch_sub_command
    tracker.create_track(cfg)
  File "/home/core/venv/lib/python3.8/site-packages/esrally/tracker/tracker.py", line 85, in create_track
    info = client.info()
  File "/home/core/venv/lib/python3.8/site-packages/elasticsearch/_sync/client/utils.py", line 414, in wrapped
    return api(*args, **kwargs)
  File "/home/core/venv/lib/python3.8/site-packages/elasticsearch/_sync/client/ __init__.py", line 2296, in info
    return self.perform_request( # type: ignore[return-value]
  File "/home/core/venv/lib/python3.8/site-packages/esrally/client/synchronous.py", line 170, in perform_request
    _ProductChecker.raise_error(self._verified_elasticsearch, info_meta, info_body)
  File "/home/core/venv/lib/python3.8/site-packages/esrally/client/synchronous.py", line 74, in raise_error
    raise UnsupportedProductError(message, meta=meta, body=body)
elasticsearch.UnsupportedProductError: The client noticed that the server is not Elasticsearch and we do not support this unknown product

```

I hope the info is enough, if anything is missing pls highlight

---

<div class="post-metadata">

**Author:** ![gbanasiak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gbanasiak/32/121454_2.png) [@gbanasiak](https://discuss.elastic.co/u/gbanasiak)\
**Post date:** [June 14, 2023, 12:56pm UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/9 "2023-06-14T12:56:33Z")

</div>

Thank you for sharing.

You're using very old Elasticsearch version `5.6.16` which is not supported by Rally, see [Elasticsearch Version Support - Rally 2.8.0 documentation](https://esrally.readthedocs.io/en/stable/versions.html?highlight=elasticsearch%20version#minimum-supported-version).

---

<div class="post-metadata">

**Author:** ![Darshan\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_j/32/119447_2.png) [@Darshan\_J](https://discuss.elastic.co/u/Darshan_J)\
**Post date:** [June 15, 2023, 4:25am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/10 "2023-06-15T04:25:44Z")

</div>

Thanks for taking your time and helping out.  
Is there any lower version of rally that supports ES of v5.

---

<div class="post-metadata">

**Author:** ![gbanasiak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gbanasiak/32/121454_2.png) [@gbanasiak](https://discuss.elastic.co/u/gbanasiak)\
**Post date:** [June 15, 2023, 7:17am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/11 "2023-06-15T07:17:22Z")

</div>

Official support for Elasticsearch 5.x was dropped in [this](https://github.com/elastic/rally/pull/1237) PR, in Rally version `2.2.0`. Formally you would need to use Rally `2.1.0` or older.

The recommended option is to upgrade Elasticsearch cluster to [supported version](https://www.elastic.co/support/eol), and use most recent Rally version.

---

<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:** [July 13, 2023, 7:17am UTC](https://discuss.elastic.co/t/benchmarking-using-esrally/335735/12 "2023-07-13T07:17:24Z")

</div>

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