# Shard limit hit **URL:** \ **Category:** Elasticsearch\ **Created:** [March 12, 2018, 5:45pm UTC](https://discuss.elastic.co/t/shard-limit-hit/123606 "2018-03-12T17:45:36Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![pixelrebel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pixelrebel/32/14056_2.png) [@pixelrebel](https://discuss.elastic.co/u/pixelrebel)\ **Post date:** [March 12, 2018, 6:22pm UTC](https://discuss.elastic.co/t/shard-limit-hit/123606/6 "2018-03-12T18:22:58Z")
1000 is the default. Your admin either neglected to migrate this custom setting over, or more likely, your admin may have increased the number of shards per index on your new cluster. Ideally, you will want to keep within the recommended settings and rewrite logic around the limitations. That said, I think I found a post with the answer you are looking for. Changing the limit is a cluster setting that will need to be configured by an administrator: > [@Action.search.shard\_count.limit exceeded](https://discuss.elastic.co/t/action-search-shard-count-limit-exceeded/62891): > > Can someone please help locate the file containing this parameter action.search.shard\_count.limit I trying to parse a single log file of around 3.2 GB using ELK stack. The same has got indexed and when I am trying to discover indexed logs in Kibana I get the following error. Error: Discover: Trying to query 2051 shards, which is over the limit of 1000. This limit exists because querying many shards at the same time can make the job of the coordinating node very CPU and/or memory intensive. It… --- _[View the full topic](https://discuss.elastic.co/t/shard-limit-hit/123606)._