# Elasticsearch continually fails after upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [June 12, 2019, 11:20pm UTC](https://discuss.elastic.co/t/elasticsearch-continually-fails-after-upgrade/185528 "2019-06-12T23:20:12Z")\ **Posts on this page:** 1\ **Showing post:** 8
**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:** [June 13, 2019, 3:52am UTC](https://discuss.elastic.co/t/elasticsearch-continually-fails-after-upgrade/185528/8 "2019-06-13T03:52:14Z")
Have a look at [Kibana only display logo no content -elasticsearch error shard - #11 by warkolm](https://discuss.elastic.co/t/kibana-only-display-logo-no-content-elasticsearch-error-shard/185529/11) to help with reindexing. > [@Emersumbigens](#): > > Wanting to do something basic, which I thought could be accomplished by a single index or maybe a single index per filebeat type. Not yet sure where all the indexes came from or what led to such a high shard count. I didn't configure a shard count anywhere. Indices are where the data is stored, they are made of shards. In the 6.X release we defaulted to 5 shards per index with 1 replica set, so a total of 10 per index. We changed that in 7.X to be 1 per index with 1 replica (ie 2). > [@Emersumbigens](#): > > If I do a complete reinstall, is there a way for me to set the shard count? No need to do that! 🙂 Though I would suggest using the latest 7.X release, as it reduces the burden here. Otherwise you can set the shard count in the filebeat config file. --- _[View the full topic](https://discuss.elastic.co/t/elasticsearch-continually-fails-after-upgrade/185528)._