# Shards Failing **URL:** \ **Category:** Elasticsearch\ **Created:** [July 21, 2018, 4:47am UTC](https://discuss.elastic.co/t/shards-failing/140978 "2018-07-21T04:47:21Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Sulaiman](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Sulaiman](https://discuss.elastic.co/u/Sulaiman)\ **Post date:** [July 21, 2018, 4:47am UTC](https://discuss.elastic.co/t/shards-failing/140978/1 "2018-07-21T04:47:21Z")
Recently I have upgrade ElasticSearch version "6.3.1" but I am facing too many shards failing with old data. I am using Elastic search with kibana,logstash, wazuh curl -XGET localhost:9200/\_cat/shards?h=index,shard,prirep,state,unassigned.reason| grep UNASSIGNED % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 14 108k 14 16300 0 0 8260 0 0:0wazuh-alerts-3.x-2018.05.23 3 p UNASSIGNED CLUSTER\_RECOVERED 0:13 wazuh-alerts-3.x-2018.05.23 3 r UNASSIGNED CLUSTER\_RECOVERED 0:0wazuh-alerts-3.x-2018.05.23 2 p UNASSIGNED CLUSTER\_RECOVERED 0:01wazuh-alerts-3.x-2018.05.23 2 r UNASSIGNED CLUSTER\_RECOVERED 0:wazuh-alerts-3.x-2018.05.23 4 p UNASSIGNED CLUSTER\_RECOVERED 00:1wazuh-alerts-3.x-2018.05.23 4 r UNASSIGNED CLUSTER\_RECOVERED 2 8wazuh-alerts-3.x-2018.05.23 1 p UNASSIGNED CLUSTER\_RECOVERED 257wazuh-alerts-3.x-2018.05.23 1 r UNASSIGNED CLUSTER\_RECOVERED wazuh-alerts-3.x-2018.05.23 0 p UNASSIGNED CLUSTER\_RECOVERED wazuh-alerts-3.x-2018.05.23 0 r UNASSIGNED CLUSTER\_RECOVERED wazuh-monitoring-3.x-2018.06.27 3 r UNASSIGNED CLUSTER\_RECOVERED wazuh-monitoring-3.x-2018.06.27 2 r UNASSIGNED CLUSTER\_RECOVERED wazuh-monitoring-3.x-2018.06.27 4 r UNASSIGNED CLUSTER\_RECOVERED Nodes: 1 Indices: 166 Total Shards: 1893 Unassigned Shards: 1192 Documents: 24,129,219 Data: 13.8 GB Health: red Red ---
**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:** [July 21, 2018, 5:33am UTC](https://discuss.elastic.co/t/shards-failing/140978/2 "2018-07-21T05:33:14Z")
You probably have too many shards per node. May I suggest you look at the following resources about sizing: [https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing) > **[How many shards should I have in my Elasticsearch cluster? | Elastic](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)** > > Elasticsearch is a very versatile platform, that supports a variety of use cases, and provides great flexibility around data organisation and replication strategies. This flexibility can however somet... > **[NetSecureDay: Managing your Black Friday Logs](https://speakerdeck.com/elastic/netsecureday-managing-your-black-friday-logs)** > > Surveiller une application complexe n’est pas une tâche aisée, mais avec les bons outils, ce n’est pas si sorcier. Néanmoins, des périodes fortes telles que les opérations de type « Black Friday » (Vendredi noir) ou période de Noël peuvent pousser... ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 18, 2018, 5:36am UTC](https://discuss.elastic.co/t/shards-failing/140978/3 "2018-08-18T05:36:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.