# Elastic search cluster health is always red

**URL:** <https://discuss.elastic.co/t/elastic-search-cluster-health-is-always-red/175396>\
**Category:** Elasticsearch\
**Created:** [April 4, 2019, 11:06am UTC](https://discuss.elastic.co/t/elastic-search-cluster-health-is-always-red/175396 "2019-04-04T11:06:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hemamalini](https://avatars.discourse-cdn.com/v4/letter/h/7feea3/32.png) [@hemamalini](https://discuss.elastic.co/u/hemamalini)\
**Post date:** [April 4, 2019, 11:06am UTC](https://discuss.elastic.co/t/elastic-search-cluster-health-is-always-red/175396/1 "2019-04-04T11:06:01Z")

</div>

Elastic search version - 5.6.14 with kibana is installed using MPack - elasticsearch\_mpack-0.7.1.0.tar.gz in centos7.

Below is the elasticsearch.yml configuration

cluster:  
name: metron  
routing:  
allocation.node\_concurrent\_recoveries: 4  
allocation.disk.watermark.low: .97  
allocation.disk.threshold\_enabled: true  
allocation.disk.watermark.high: 0.99

discovery:  
zen:  
ping:  
unicast:  
hosts: ["10.101.10.1"]

node:  
data: true  
master: true  
name: node1  
path:  
data: "/opt/lmm/es\_data"

http:  
port: 9200-9300  
cors.enabled: "false"

transport:  
tcp:  
port: 9300-9400

gateway:  
recover\_after\_data\_nodes: 3  
recover\_after\_time: 15m  
expected\_data\_nodes: 0

# [Indexing Performance Tips | Elasticsearch: The Definitive Guide [2.x] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/current/indexing-performance.html)

indices:  
store.throttle.type: none  
memory:  
index\_buffer\_size: 10%  
fielddata:  
cache.size: 25%

bootstrap:  
memory\_lock: true  
system\_call\_filter: false

thread\_pool:  
bulk:  
queue\_size: 3000  
index:  
queue\_size: 1000

discovery.zen.ping\_timeout: 5s  
discovery.zen.fd.ping\_interval: 15s  
discovery.zen.fd.ping\_timeout: 60s  
discovery.zen.fd.ping\_retries: 5  
discovery.zen.minimum\_master\_nodes: 1

network.host: ["10.101.10.1']  
network.publish\_host:

Kibana.yml

# Kibana is served by a back end server. This controls which port to use.

server.port: 5000

# The host to bind the server to.

# Kibana (like Elasticsearch) now binds to localhost for security purposes instead of 0.0.0.0 (all addresses). Previous binding to 0.0.0.0 also caused issues for Windows users.

server.host: 10.101.10.1

I am getting below exception when i tried with the url - [http://10.101.10.1:9200/\_cat/indices?v](http://10.101.10.1:9200/_cat/indices?v)

> {"error":{"root\_cause":[{"type":"cluster\_block\_exception","reason":"blocked by: [SERVICE\_UNAVAILABLE/1/state not recovered / initialized];"}],"type":"cluster\_block\_exception","reason":"blocked by: [SERVICE\_UNAVAILABLE/1/state not recovered / initialized];"},"status":503}

URL -[http://10.101.10.1:9200/\_cat/health?v](http://10.101.10.1:9200/_cat/health?v)

epoch timestamp cluster status node.total node.data shards pri relo init unassign pending\_tasks max\_task\_wait\_time active\_shards\_percent  
1554375934 16:35:34 metron red 1 1 0 0 0 0 0 0 - NaN%

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 4, 2019, 12:38pm UTC](https://discuss.elastic.co/t/elastic-search-cluster-health-is-always-red/175396/2 "2019-04-04T12:38:30Z")

</div>

Here is a blog post about what to do to investigate a red cluster:

> **[RED Elasticsearch Cluster? Panic no longer](https://www.elastic.co/blog/red-elasticsearch-cluster-panic-no-longer)**
>
> Your cluster is RED - you have unassigned shards and your cluster is not fully operational. Introducing a new Elasticsearch API which will save the day.

It'd be best to start with these suggestions; if you have more specific questions then please feel free to ask.

---

<div class="post-metadata">

**Author:** ![hemamalini](https://avatars.discourse-cdn.com/v4/letter/h/7feea3/32.png) [@hemamalini](https://discuss.elastic.co/u/hemamalini)\
**Post date:** [April 8, 2019, 11:09am UTC](https://discuss.elastic.co/t/elastic-search-cluster-health-is-always-red/175396/3 "2019-04-08T11:09:42Z")

</div>

thanks for the link. Issue is resolved after changing the below properties

gateway:  
recover\_after\_data\_nodes: 1  
recover\_after\_time: 15m  
expected\_data\_nodes: 1

---

<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:** [May 6, 2019, 11:09am UTC](https://discuss.elastic.co/t/elastic-search-cluster-health-is-always-red/175396/4 "2019-05-06T11:09:47Z")

</div>

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