# Geeting "Status : RED " error **URL:** \ **Category:** Elasticsearch\ **Created:** [February 28, 2018, 7:38am UTC](https://discuss.elastic.co/t/geeting-status-red-error/121799 "2018-02-28T07:38:54Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![madurad](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@madurad](https://discuss.elastic.co/u/madurad)\ **Post date:** [February 28, 2018, 7:38am UTC](https://discuss.elastic.co/t/geeting-status-red-error/121799/1 "2018-02-28T07:38:54Z")
My Elastic search server contains 88GB of indices in lib file, and my server runs out of memory. Any possibility to delete some older files here? ![kibana-error](https://us1.discourse-cdn.com/elastic/original/3X/3/9/3928fc8476200aa0a9c27ca5fff63493c2c85a58.JPG) Any help ? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [February 28, 2018, 12:16pm UTC](https://discuss.elastic.co/t/geeting-status-red-error/121799/2 "2018-02-28T12:16:21Z")
This? ``` curl -XDELETE host:9200/indexname ``` ---
**Author:** ![madurad](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@madurad](https://discuss.elastic.co/u/madurad)\ **Post date:** [March 5, 2018, 2:02pm UTC](https://discuss.elastic.co/t/geeting-status-red-error/121799/3 "2018-03-05T14:02:17Z")
Kibana has been installed with Docker and docker image getting increases it's capacity up to 96GB of my hard drive. Under docker, I can see following files with the capacity. | 5.8G | aufs | | --- | --- | | 220M | containers | | 5.4M | image | | 60K | network | | 20K | plugins | | 4.0K | swarm | | 4.0K | tmp | | 4.0K | trust | | 90G | volumes | ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 5, 2018, 3:15pm UTC](https://discuss.elastic.co/t/geeting-status-red-error/121799/4 "2018-03-05T15:15:17Z")
You said Elasticsearch and now you mention Kibana. I'm kind of confused. Anyway, can you run: ```auto curl localhost:9200/_cat/indices?v ``` ---
**Author:** ![madurad](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@madurad](https://discuss.elastic.co/u/madurad)\ **Post date:** [March 6, 2018, 3:18am UTC](https://discuss.elastic.co/t/geeting-status-red-error/121799/5 "2018-03-06T03:18:04Z")
Hi David, Sorry for the confusion, I ran the command that you asked, and please find some of results given below. > health status index uuid pri rep docs.count docs.deleted store.size pri.store.size > yellow open %{[@metadata][beat]}-2017.08.05 z3DA1oRISZWqev8bfDzMQA 5 1 1984 0 1.4mb 1.4mb > yellow open filebeat-2018.01.15 zMBrlqTrTxqJJoLY3rSv7w 5 1 1419561 0 435.1mb 435.1mb > yellow open filebeat-2017.06.26 \_E40ZJhOQveBkHpRz9ey7w 5 1 9 0 77.5kb 77.5kb > yellow open %{[@metadata][beat]}-2017.08.29 Bj8pNf2fSvOivaJHW6226A 5 1 3773 0 2.5mb 2.5mb > yellow open filebeat-2017.10.20 948D35IpRpC6bSdEPaSNFw 5 1 1005189 0 352.1mb 352.1mb > yellow open %{[@metadata][beat]}-2018.02.20 GJs\_bb2aTkyt2Dr9uSiH6w 5 1 4343 0 3.2mb 3.2mb > yellow open %{[@metadata][beat]}-2017.08.25 313yZjcMQj-DTsp8XXQ97Q 5 1 3749 0 2.6mb 2.6mb > yellow open filebeat-2017.07.23 EuTUspOqRiKwEOq2gUUkMw 5 1 342733 0 109.8mb 109.8mb > yellow open %{[@metadata][beat]}-2018.02.19 xE-QEWIrQ9-WJdN\_SLBRZw 5 1 4764 0 3.5mb 3.5mb > yellow open %{[@metadata][beat]}-2017.09.11 6DHHZ8ENSxKfiRqgZp7YNQ 5 1 2757 0 2.1mb 2.1mb > yellow open filebeat-2017.08.04 w\_fwESQvQYqccBQHwWkiLQ 5 1 441758 0 120.6mb 120.6mb ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 6, 2018, 1:45pm UTC](https://discuss.elastic.co/t/geeting-status-red-error/121799/6 "2018-03-06T13:45:58Z")
It looks like you have a lot of small indices and shards in your cluster, as well as some that indicate a problem with your ingest configuration, e.g. `%{[@metadata][beat]}-2018.02.19`. I would recommend that you read [this blog post](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster). To get a better understanding of the state of the cluster, what is the full output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/cluster-stats.html)? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 3, 2018, 1:46pm UTC](https://discuss.elastic.co/t/geeting-status-red-error/121799/7 "2018-04-03T13:46:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.