# How to solve red indices **URL:** \ **Category:** Elasticsearch\ **Created:** [March 22, 2016, 10:55pm UTC](https://discuss.elastic.co/t/how-to-solve-red-indices/45167 "2016-03-22T22:55:37Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![yahoo](https://avatars.discourse-cdn.com/v4/letter/y/898d66/32.png) [@yahoo](https://discuss.elastic.co/u/yahoo)\ **Post date:** [March 22, 2016, 10:55pm UTC](https://discuss.elastic.co/t/how-to-solve-red-indices/45167/1 "2016-03-22T22:55:37Z")
How to diagnose and solve the red indices? { "cluster\_name": "clus\_1", "status": "red", "timed\_out": false, "number\_of\_nodes": 1, "number\_of\_data\_nodes": 1, "active\_primary\_shards": 3, "active\_shards": 3, "relocating\_shards": 0, "initializing\_shards": 0, "unassigned\_shards": 3, "delayed\_unassigned\_shards": 0, "number\_of\_pending\_tasks": 0, "number\_of\_in\_flight\_fetch": 0, "task\_max\_waiting\_in\_queue\_millis": 0, "active\_shards\_percent\_as\_number": 50.0 } ``` health status index pri rep docs.count docs.deleted store.size pri.store.size red open l-2016.02.06 1 0 red open l-2016.03.15 1 0 yellow open .kibana 1 1 11 1 49.7kb 49.7kb green open l-2016.03.14 1 0 3929 0 1.4mb 1.4mb green open l-2016.02.05 1 0 1701 0 1.1mb 1.1mb ``` ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 23, 2016, 3:22am UTC](https://discuss.elastic.co/t/how-to-solve-red-indices/45167/2 "2016-03-23T03:22:00Z")
Check your ES logs, they should say something. ---
**Author:** ![yahoo](https://avatars.discourse-cdn.com/v4/letter/y/898d66/32.png) [@yahoo](https://discuss.elastic.co/u/yahoo)\ **Post date:** [March 23, 2016, 6:43pm UTC](https://discuss.elastic.co/t/how-to-solve-red-indices/45167/3 "2016-03-23T18:43:06Z")
The ES log does not reveal much. ``` [2016-03-23 17:49:20,284][WARN][bootstrap] unable to install syscall filter: syscall filtering not supported for OS: 'Windows 10' [2016-03-23 17:49:21,125][INFO][node] [node_1] version[2.1.1], pid[5084], build[40e2c53/2015-12-15T13:05:55Z] [2016-03-23 17:49:21,126][INFO][node] [node_1] initializing ... [2016-03-23 17:49:21,197][INFO][plugins] [node_1] loaded [], sites [] [2016-03-23 17:49:21,224][INFO][env] [node_1] using [1] data paths, mounts [[OS (C:)]], net usable_space [377.5gb], net total_space [448.2gb], spins? [unknown], types [NTFS] [2016-03-23 17:49:26,257][INFO][node] [node_1] initialized [2016-03-23 17:49:26,257][INFO][node] [node_1] starting ... [2016-03-23 17:49:26,674][INFO][transport] [node_1] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300} [2016-03-23 17:49:26,691][INFO][discovery] [node_1] clus_1/m01X78DnTX2iztJDALuTXA [2016-03-23 17:49:30,735][INFO][cluster.service] [node_1] new_master {node_1}{m01X78DnTX2iztJDALuTXA}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected_as_master, [0] joins received) [2016-03-23 17:49:30,799][INFO][http] [node_1] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200} [2016-03-23 17:49:30,800][INFO][node] [node_1] started [2016-03-23 17:49:31,408][INFO][gateway] [node_1] recovered [5] indices into cluster_state ``` ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 23, 2016, 8:02pm UTC](https://discuss.elastic.co/t/how-to-solve-red-indices/45167/4 "2016-03-23T20:02:10Z")
That's unusual. Did you have a node problem that forced a shutdown or something similar? ---
**Author:** ![yahoo](https://avatars.discourse-cdn.com/v4/letter/y/898d66/32.png) [@yahoo](https://discuss.elastic.co/u/yahoo)\ **Post date:** [March 23, 2016, 11:04pm UTC](https://discuss.elastic.co/t/how-to-solve-red-indices/45167/5 "2016-03-23T23:04:51Z")
Hi @warkolm I did not have a node problem. However, I may forced a shutdown through killing the window that was running elasticsearch. I found this entry through an old log. It may be related to the problem. ``` [2016-03-19 19:13:17,015][INFO][node] [node_1] stopping ... [2016-03-19 19:13:17,031][WARN][netty.channel.DefaultChannelPipeline] An exception was thrown by an exception handler. java.util.concurrent.RejectedExecutionException: Worker has already been shutdown ``` Nevertheless, how can I solve this problem? Please advice me if there is a better way I can delete the indices from ES. Then I have to tell Logstash to re-read these particular indices by editing the config file. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 23, 2016, 11:23pm UTC](https://discuss.elastic.co/t/how-to-solve-red-indices/45167/6 "2016-03-23T23:23:31Z")
You will probably need to delete those indices and then reindex. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:05pm UTC](https://discuss.elastic.co/t/how-to-solve-red-indices/45167/7 "2017-07-05T23:05:41Z")