# Grafana Shard Limit 1000

**URL:** <https://discuss.elastic.co/t/grafana-shard-limit-1000/77298>\
**Category:** Elasticsearch\
**Created:** [March 3, 2017, 10:35am UTC](https://discuss.elastic.co/t/grafana-shard-limit-1000/77298 "2017-03-03T10:35:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ariceELK](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@ariceELK](https://discuss.elastic.co/u/ariceELK)\
**Post date:** [March 3, 2017, 10:35am UTC](https://discuss.elastic.co/t/grafana-shard-limit-1000/77298/1 "2017-03-03T10:35:35Z")

</div>

Hi,

Im using ES v5.2.0 and Grafana v4.1

Im getting an error in Grafana when the number of shards in ES is over 1000. Grafana won't display any data.

Is there a setting to increase this limit ?

Thanks  
Aidan

---

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [March 3, 2017, 11:02am UTC](https://discuss.elastic.co/t/grafana-shard-limit-1000/77298/2 "2017-03-03T11:02:18Z")

</div>

From the [docs](https://www.elastic.co/guide/en/elasticsearch/reference/5.2/search-search.html):

> By default elasticsearch rejects search requests that would query more than 1000 shards. The reason is that such large numbers of shards make the job of the coordinating node very CPU and memory intensive. It is usually a better idea to organize data in such a way that there are fewer larger shards. In case you would like to bypass this limit, which is discouraged, you can update the action.search.shard\_count.limit cluster setting to a greater value.

---

<div class="post-metadata">

**Author:** ![ariceELK](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@ariceELK](https://discuss.elastic.co/u/ariceELK)\
**Post date:** [March 6, 2017, 4:27pm UTC](https://discuss.elastic.co/t/grafana-shard-limit-1000/77298/3 "2017-03-06T16:27:33Z")

</div>

thank you...

---

<div class="post-metadata">

**Author:** ![ariceELK](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@ariceELK](https://discuss.elastic.co/u/ariceELK)\
**Post date:** [March 14, 2017, 1:26pm UTC](https://discuss.elastic.co/t/grafana-shard-limit-1000/77298/4 "2017-03-14T13:26:43Z")

</div>

Hi,

I have another related issue.  
We are using fields.ipaddr as a text sting and both grafana and elasticsearch are complaining, advising to add it to fielddata. fielddata=true on [fields.ipaddr]

PUT filebeat-\*/\_mapping/my\_type  
{  
"properties": {  
"my\_field": { "fields.ipaddr"  
"type": "text",  
"fielddata": true  
}  
}  
}

is failing to parse the content to map ?

Brgds  
Aidan

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 11, 2017, 1:26pm UTC](https://discuss.elastic.co/t/grafana-shard-limit-1000/77298/5 "2017-04-11T13:26:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.