# Limiting size of shard data

**URL:** <https://discuss.elastic.co/t/limiting-size-of-shard-data/13733>\
**Category:** Elasticsearch\
**Created:** [September 24, 2013, 10:24am UTC](https://discuss.elastic.co/t/limiting-size-of-shard-data/13733 "2013-09-24T10:24:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lee\_Briggs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lee_briggs/32/2090_2.png) [@Lee\_Briggs](https://discuss.elastic.co/u/Lee_Briggs)\
**Post date:** [September 24, 2013, 10:24am UTC](https://discuss.elastic.co/t/limiting-size-of-shard-data/13733/1 "2013-09-24T10:24:19Z")

</div>

Hi there,

We recently had a problem with our elasticsearch cluster which resulted in  
the shard data filling a partition. Without going into too many details, is  
there a setting within elasticsearch which can limit the size of the shard  
data? If there isn't, how can we stop this happening within the application?

I am going to re-partition and move the directory of elasticsearch to  
mitigate this problem in the future, but I would also like to know if  
there's a way for elasticsearch to stop allocating shards to a node if a  
size limit is reached?

Any help appreciated.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [September 24, 2013, 1:17pm UTC](https://discuss.elastic.co/t/limiting-size-of-shard-data/13733/2 "2013-09-24T13:17:09Z")

</div>

This has been fixed recently by introducing a disk space aware shard  
allocator. See this pull request

> <https://github.com/elastic/elasticsearch/pull/3637>

If you want to take advance of it, you'll have to update to the latest ES  
release.

Jörg

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [July 6, 2017, 2:14am UTC](https://discuss.elastic.co/t/limiting-size-of-shard-data/13733/3 "2017-07-06T02:14:56Z")

</div>


