# Controlling Stored Data Size **URL:** \ **Category:** Elasticsearch\ **Created:** [August 28, 2013, 2:35pm UTC](https://discuss.elastic.co/t/controlling-stored-data-size/13368 "2013-08-28T14:35:07Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Michael\_Leikind](https://avatars.discourse-cdn.com/v4/letter/m/df788c/32.png) [@Michael\_Leikind](https://discuss.elastic.co/u/Michael_Leikind)\ **Post date:** [August 28, 2013, 2:35pm UTC](https://discuss.elastic.co/t/controlling-stored-data-size/13368/1 "2013-08-28T14:35:07Z")
Greetings! I plain to use elasticache with logstash. Our production servers send about 20G of logs per day, so indexing server may run out of disk space very soon. On my current system (which I want to replace) I have a control over indexed data rolling mechanism, i.e. I can configure it to archive the old data and after a some period of time remove it completely from index DB. Tried to search for an alternative configuration in elasticsearch, but with no luck. Can you please advise on what my options are ? -- 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). ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [September 12, 2013, 9:58am UTC](https://discuss.elastic.co/t/controlling-stored-data-size/13368/2 "2013-09-12T09:58:55Z")
Hey, right now there is no expire on indices, but this might come sooner or later, see [Allow setting ttl at index level · Issue #2114 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2114) Apart from that you can use time based indices (per month), combine them for search via aliases, and maybe delete them manually via a cronjob at the beginning of each month, or even have a small monitoring script, which checks the available space and then deletes the oldest data automatically for now. Hope this helps... --Alex On Wed, Aug 28, 2013 at 4:35 PM, Michael Leikind \< [michael.leikind@cloudon.com](mailto:michael.leikind@cloudon.com)\> wrote: > Greetings! > I plain to use elasticache with logstash. > Our production servers send about 20G of logs per day, so indexing server > may run out of disk space very soon. > On my current system (which I want to replace) I have a control over > indexed data rolling mechanism, i.e. I can configure it to archive the old > data and after a some period of time remove it completely from index DB. > Tried to search for an alternative configuration in elasticsearch, but > with no luck. > Can you please advise on what my options are ? > > -- > 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). -- 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). ---
**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:16am UTC](https://discuss.elastic.co/t/controlling-stored-data-size/13368/3 "2017-07-06T02:16:57Z")