How to run rally against an existing on-premise cluster

I am running my elasticsearch (version 7.11) cluster on an on-premise kubernetes cluster. security is enabled in the cluster. to run rally i have created a separate pod

apiVersion: v1

    kind: Pod


      name: {{ template "fullname" . }}



      - name: esrally

        image: {{ .Values.image }}


          - "sleep"

          - "604800"

      {{- if .Values.reportDir }}


        - name: report

          mountPath: {{ .Values.reportDir }}

      restartPolicy: Never


      - name: report


          path: {{ .Values.reportDir }}

      {{ end }}


image: elastic/rally
reportDir: /tmp
reportFile: report-mem-lock.csv


config.version = 17

[system] = local

root.dir = /rally/.rally/benchmarks
src.root.dir = /rally/.rally/benchmarks/src

remote.repo.url =
elasticsearch.src.subdir = elasticsearch

local.dataset.cache = /rally/.rally/benchmarks/data

datastore.type = in-memory =
datastore.port = = False
datastore.user =
datastore.password =

default.url =

default.url =

preserve_benchmark_candidate = false

release.cache = true

We are running behind a proxy, so i have set up http_proxy and verified that rally is able to get tracks
proxy setting
Command -
esrally race --track=geonames --pipeline=benchmark-only --test-mode --kill-running-processes --client-options="timeout:60,use_ssl:true,verify_certs:false,basic_auth_user:'elastic',basic_auth_password:'password'"

Getting the following error -

[WARNING] No Internet connection detected. Automatic download of track data sets etc. is disabled.
[ERROR] Cannot race. Error in race control (ConnectionError(<urllib3.connection.HTTPSConnection object at 0x7f621b4bca60>: Failed to establish a new connection: [Errno -2] Name or service not known) caused by: NewConnectionError(<urllib3.connection.HTTPSConnection object at 0x7f621b4bca60>: Failed to establish a new connection: [Errno -2] Name or service not known))

Hi! Name or service not known should indicate that your pod cannot resolve the address you gave to --target-hosts. Without going too deep here, consider:

Is there a defined Service name that you're hitting?
Is the service for ES in the same namespace as the rally pod?
If not, are you using the FQDN for the target service?

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