# It's too slow when checking a non-exist index's health status

**URL:** <https://discuss.elastic.co/t/its-too-slow-when-checking-a-non-exist-indexs-health-status/10236>\
**Category:** Elasticsearch\
**Created:** [January 6, 2013, 7:05am UTC](https://discuss.elastic.co/t/its-too-slow-when-checking-a-non-exist-indexs-health-status/10236 "2013-01-06T07:05:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![asoqa](https://avatars.discourse-cdn.com/v4/letter/a/f0a364/32.png) [@asoqa](https://discuss.elastic.co/u/asoqa)\
**Post date:** [January 6, 2013, 7:05am UTC](https://discuss.elastic.co/t/its-too-slow-when-checking-a-non-exist-indexs-health-status/10236/1 "2013-01-06T07:05:20Z")

</div>

for example:  
curl -XGET  
'[http://localhost:9200/\_cluster/health/not\_exist\_index?pretty=true](http://localhost:9200/_cluster/health/not_exist_index?pretty=true)'

when executing this request, it's too slow.

My es version is 0.19.11, and contains only two nodes and only several  
indices with defalut shard settings.

--

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [January 6, 2013, 10:37pm UTC](https://discuss.elastic.co/t/its-too-slow-when-checking-a-non-exist-indexs-health-status/10236/2 "2013-01-06T22:37:02Z")

</div>

It will wait for the configured timeout to see maybe the index will be created. You can pass timeout=0 and then it will return right away with a RED status.

If you want to check if an index exists or not, you can use the index exists API.

On Jan 6, 2013, at 8:05 AM, asoqa [asoqa51@gmail.com](mailto:asoqa51@gmail.com) wrote:

> for example:  
> curl -XGET '[http://localhost:9200/\_cluster/health/not\_exist\_index?pretty=true](http://localhost:9200/_cluster/health/not_exist_index?pretty=true)'
> 
> when executing this request, it's too slow.
> 
> My es version is 0.19.11, and contains only two nodes and only several indices with defalut shard settings.
> 
> --

--

---

<div class="post-metadata">

**Author:** ![asoqa](https://avatars.discourse-cdn.com/v4/letter/a/f0a364/32.png) [@asoqa](https://discuss.elastic.co/u/asoqa)\
**Post date:** [January 7, 2013, 6:50am UTC](https://discuss.elastic.co/t/its-too-slow-when-checking-a-non-exist-indexs-health-status/10236/3 "2013-01-07T06:50:21Z")

</div>

thanks, I see.

在 2013年1月7日星期一UTC+8上午6时37分02秒，kimchy写道：

> It will wait for the configured timeout to see maybe the index will be  
> created. You can pass timeout=0 and then it will return right away with a  
> RED status.
> 
> If you want to check if an index exists or not, you can use the index  
> exists API.
> 
> On Jan 6, 2013, at 8:05 AM, asoqa \<[aso...@gmail.com](mailto:aso...@gmail.com) \<javascript:\>\> wrote:
> 
> > for example:  
> > curl -XGET '  
> > [http://localhost:9200/\_cluster/health/not\_exist\_index?pretty=true](http://localhost:9200/_cluster/health/not_exist_index?pretty=true)'
> > 
> > when executing this request, it's too slow.
> > 
> > My es version is 0.19.11, and contains only two nodes and only several  
> > indices with defalut shard settings.
> > 
> > --

--

---

<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 6, 2017, 2:57am UTC](https://discuss.elastic.co/t/its-too-slow-when-checking-a-non-exist-indexs-health-status/10236/4 "2017-07-06T02:57:37Z")

</div>