# Esrally gets stuck on check-cluster-health

**URL:** <https://discuss.elastic.co/t/esrally-gets-stuck-on-check-cluster-health/291264>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [December 8, 2021, 9:09pm UTC](https://discuss.elastic.co/t/esrally-gets-stuck-on-check-cluster-health/291264 "2021-12-08T21:09:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![json](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/json/32/4125_2.png) [@json](https://discuss.elastic.co/u/json)\
**Post date:** [December 8, 2021, 10:38pm UTC](https://discuss.elastic.co/t/esrally-gets-stuck-on-check-cluster-health/291264/2 "2021-12-08T22:38:19Z")

</div>

Hi Alpha,

Would you mind running your `curl` check using the same endpoint as Rally? I.e.,

```auto
curl 'http://127.0.0.1:39200/_cluster/health/nyc_taxis?wait_for_status=green&wait_for_no_relocating_shards=false'

```

Also, make sure there are no other process leftovers from other `esrally` executions.

Can you share more of `rally.log`, preferably the complete file and any customized configurations?

`GET /_cluster/health/<index>` can behave this way for non-existing indices or if the index will never be green. `_cat/health` returns `green` because it represents the status of all known indices in the cluster.

Some possibilities:

- The `nyc_taxis` index exists but is `yellow`. This will happen if the number of index replicas has been configured to be \>0 for a single node cluster.
- `nyc_taxis` does not exist and is, therefore `red`.

See also [Rally race gets stuck on check-cluster-health](https://discuss.elastic.co/t/rally-race-gets-stuck-on-check-cluster-health/268815).

---

_[View the full topic](https://discuss.elastic.co/t/esrally-gets-stuck-on-check-cluster-health/291264)._