# Rally race gets stuck on check-cluster-health **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [March 30, 2021, 3:41pm UTC](https://discuss.elastic.co/t/rally-race-gets-stuck-on-check-cluster-health/268815 "2021-03-30T15:41:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Ellie\_Bird](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ellie_bird/32/86340_2.png) [@Ellie\_Bird](https://discuss.elastic.co/u/Ellie_Bird)\ **Post date:** [March 30, 2021, 3:41pm UTC](https://discuss.elastic.co/t/rally-race-gets-stuck-on-check-cluster-health/268815/1 "2021-03-30T15:41:30Z")
When I use the track from repository, it works without any problem. Now, I created the track data from existing cluster. and hanging at the stage of 'check-cluster-health'. I am using esrally version 2.0.4 elasticsearch version : 6.8.1 ``` > > esrally race --pipeline=benchmark-only --track-path=~/tracks/testtrack/ --target-hosts=127.0.0.1:9200 --kill-running-processes --test-mode > > ________ > / __\____ _/ / /_ __ > / /_/ / __ `/ / / / / / > / _, _/ /_/ / / / /_/ / > /_/ |_|\ __,_/_/_/\__ , / > / ____ / > > [INFO] Racing on track [testtrack] and car ['external'] with version [6.8.1]. > > [WARNING] indexing_total_time is 59 ms indicating that the cluster is not in a defined clean state. Recorded index time metrics may be misleading. > Running delete-index [100% done] > Running create-index [100% done] > Running cluster-health [0% done] > > > Here is the rally log. > 2021-03-30 15:28:43,930 ActorAddr-(T|:46065)/PID:8145 esrally.client INFO Creating ES client connected to [{'host': '127.0.0.1', 'port': 9200}] with options [{'timeout': 60, 'max_connections': 1}] > 2021-03-30 15:28:43,934 ActorAddr-(T|:44123)/PID:8146 esrally.actor INFO Worker[1] reached join point at index [6]. > 2021-03-30 15:28:43,936 ActorAddr-(T|:41685)/PID:8147 esrally.actor INFO Worker[2] is continuing its work at task index [4] on [104.595866], that is in [-1 day, 23:59:59.985102]. > 2021-03-30 15:28:43,930 ActorAddr-(T|:46065)/PID:8145 esrally.client INFO SSL support: off > 2021-03-30 15:28:43,936 ActorAddr-(T|:41685)/PID:8147 esrally.actor INFO Worker[2] reached join point at index [6]. > 2021-03-30 15:28:43,930 ActorAddr-(T|:46065)/PID:8145 esrally.client INFO HTTP basic authentication: off > 2021-03-30 15:28:43,930 ActorAddr-(T|:46065)/PID:8145 esrally.client INFO HTTP compression: off > 2021-03-30 15:28:43,927 ActorAddr-(T|:34987)/PID:8139 esrally.driver.driver INFO Scheduling next task for worker id [1] at their timestamp [104.596997] (master timestamp [104.601953]) > 2021-03-30 15:28:43,931 ActorAddr-(T|:46065)/PID:8145 esrally.driver.driver INFO Task assertions enabled: False > 2021-03-30 15:28:43,931 ActorAddr-(T|:46065)/PID:8145 esrally.driver.driver INFO Choosing [unthrottled] for [cluster-health]. > 2021-03-30 15:28:43,931 ActorAddr-(T|:46065)/PID:8145 esrally.driver.driver INFO Creating iteration-count based schedule with [None] distribution for [cluster-health] with [0] warmup iterations and [1] iterations. > 2021-03-30 15:28:43,931 ActorAddr-(T|:46065)/PID:8145 esrally.driver.driver INFO iteration-count-based schedule will determine when the schedule for [cluster-health] terminates. > 2021-03-30 15:28:43,927 ActorAddr-(T|:34987)/PID:8139 esrally.driver.driver INFO Scheduling next task for worker id [2] at their timestamp [104.595866] (master timestamp [104.601953]) > 2021-03-30 15:28:43,928 ActorAddr-(T|:34987)/PID:8139 esrally.driver.driver INFO Scheduling next task for worker id [3] at their timestamp [104.597844] (master timestamp [104.601953]) > 2021-03-30 15:28:43,932 ActorAddr-(T|:34987)/PID:8139 esrally.driver.driver INFO [1/4] workers reached join point [3/4]. > 2021-03-30 15:28:43,940 ActorAddr-(T|:34987)/PID:8139 esrally.driver.driver INFO [2/4] workers reached join point [3/4]. > 2021-03-30 15:28:43,940 ActorAddr-(T|:34987)/PID:8139 esrally.driver.driver INFO [3/4] workers reached join point [3/4]. > 2021-03-30 15:29:13,947 -not-actor-/PID:8145 elasticsearch WARNING GET http://127.0.0.1:9200/_cluster/health/testtrack-v4?wait_for_status=green&wait_for_no_relocating_shards=true [status:408 request:30.015s] ``` The cluster health is currently yellow but looks like it has to be green to complete the test? I am getting the same warning and even I killed the process, it keep generating the same warning. Is there any work-around this? Thanks in advance. ---
**Author:** ![Evgenia\_Badiyanova](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/evgenia_badiyanova/32/84068_2.png) [@Evgenia\_Badiyanova](https://discuss.elastic.co/u/Evgenia_Badiyanova)\ **Post date:** [March 30, 2021, 4:13pm UTC](https://discuss.elastic.co/t/rally-race-gets-stuck-on-check-cluster-health/268815/2 "2021-03-30T16:13:25Z")
Hello, Thank you for your interest in rally! Depending on what you have in your test track, and if you modelled it based on the existing standard tracks (eg. [geonames](https://github.com/elastic/rally-tracks/blob/5ca94442d1d6016eee7d12a48802a3a06fb71d48/geonames/challenges/default.json#L21)) there is a way to specify [what status to wait for](https://esrally.readthedocs.io/en/stable/migrate.html?highlight=cluster-health#removal-of-the-command-line-parameter-cluster-health): `--track-params="cluster_health:'yellow'".` However, please note that running performance tests on a non-green cluster may produce non-stable/non-reproducible results. Also, `--test-mode` is great to use when [debugging a track](https://esrally.readthedocs.io/en/stable/adding_tracks.html?highlight=--test-mode#adding-support-for-test-mode), but it should not be used for the actual performance benchmarks. Thanks, Evgenia ---
**Author:** ![Ellie\_Bird](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ellie_bird/32/86340_2.png) [@Ellie\_Bird](https://discuss.elastic.co/u/Ellie_Bird)\ **Post date:** [March 30, 2021, 4:22pm UTC](https://discuss.elastic.co/t/rally-race-gets-stuck-on-check-cluster-health/268815/3 "2021-03-30T16:22:40Z")
That is the trick which pass to the next task. Thanks for the quick response. ---
**Author:** ![Ellie\_Bird](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ellie_bird/32/86340_2.png) [@Ellie\_Bird](https://discuss.elastic.co/u/Ellie_Bird)\ **Post date:** [March 30, 2021, 4:23pm UTC](https://discuss.elastic.co/t/rally-race-gets-stuck-on-check-cluster-health/268815/4 "2021-03-30T16:23:37Z")
Noted for --test-mode. I thought when I added --test-mode, it will abort the hanging state. but it was same. yes of course I will not add that for the real benchmark testing. ---
**Author:** ![Ellie\_Bird](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ellie_bird/32/86340_2.png) [@Ellie\_Bird](https://discuss.elastic.co/u/Ellie_Bird)\ **Post date:** [March 30, 2021, 4:24pm UTC](https://discuss.elastic.co/t/rally-race-gets-stuck-on-check-cluster-health/268815/5 "2021-03-30T16:24:36Z")
yes when I use the track=geonames, race completes without any issues. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 27, 2021, 4:25pm UTC](https://discuss.elastic.co/t/rally-race-gets-stuck-on-check-cluster-health/268815/6 "2021-04-27T16:25:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.