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

Elastic Stack Elasticsearch
1

for example:
curl -XGET
'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.

--

2

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 wrote:

for example:
curl -XGET '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.

--

--

3

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 <javascript:>> wrote:

for example:
curl -XGET '
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.

--

--