# Reduce Disk Space Requirements **URL:** \ **Category:** Elasticsearch\ **Created:** [October 17, 2014, 10:06pm UTC](https://discuss.elastic.co/t/reduce-disk-space-requirements/20314 "2014-10-17T22:06:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![PARTH\_GANDHI](https://avatars.discourse-cdn.com/v4/letter/p/958977/32.png) [@PARTH\_GANDHI](https://discuss.elastic.co/u/PARTH_GANDHI)\ **Post date:** [October 17, 2014, 10:06pm UTC](https://discuss.elastic.co/t/reduce-disk-space-requirements/20314/1 "2014-10-17T22:06:11Z")
Details: Elastic Search version used: 1.3.4 Docs to index: ~ 2.2 Million Growth in docs: few 100 docs every week. Number of fields per doc: ~10-15 tokenizers used: ngram (min:2, max:15), path\_hierarchy filters used: word\_delimiter, pattern\_capture, lowercase, unique Size on disk: ~ 150 GB (No replicas are active) Problem: Unfortunately, I don't have the luxury of a lot of free disk space at my disposal. Why? [Let me just say I work for a too big-to-fail organizations, if you know what I mean :-)] I need to reduce my index storage footprint by at least 50%. Solutions tried: 1. run \_flush & \_optimize on the index. Didn't affect the size on disk. 2. decrease the number of primary shards from 5 to 2 (realized this is a useless attempt as number of shards doesn't affect disk space) 3. Looked into archiving the index after closing (can't use this solution as I want our users to search through all of the 2.2 Million docs, so can't archive partial docs) Can you guys suggest any other options to reduce index disk size? Your inputs are much appreciated. Thanks, Parth Gandhi -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/e343c173-da25-4281-8909-cea62cfdf6f3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e343c173-da25-4281-8909-cea62cfdf6f3%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [October 17, 2014, 10:17pm UTC](https://discuss.elastic.co/t/reduce-disk-space-requirements/20314/2 "2014-10-17T22:17:43Z")
ngram min=2 kills your index space. Use min=3 or higher. Also maybe edge ngram tokenizer might be an alternative. Jörg On Sat, Oct 18, 2014 at 12:06 AM, PARTH GANDHI [parth.gandhi85@gmail.com](mailto:parth.gandhi85@gmail.com) wrote: > Details: > Elastic Search version used: 1.3.4 > Docs to index: ~ 2.2 Million > Growth in docs: few 100 docs every week. > Number of fields per doc: ~10-15 > tokenizers used: ngram (min:2, max:15), path\_hierarchy > filters used: word\_delimiter, pattern\_capture, lowercase, unique > Size on disk: ~ 150 GB (No replicas are active) > > Problem: > Unfortunately, I don't have the luxury of a lot of free disk space at my > disposal. > Why? [Let me just say I work for a too big-to-fail organizations, if you > know what I mean :-)] > I need to reduce my index storage footprint by at least 50%. > > Solutions tried: > > 1. run \_flush & \_optimize on the index. Didn't affect the size on disk. > 2. decrease the number of primary shards from 5 to 2 (realized this is a > useless attempt as number of shards doesn't affect disk space) > 3. Looked into archiving the index after closing (can't use this solution > as I want our users to search through all of the 2.2 Million docs, so can't > archive partial docs) > > Can you guys suggest any other options to reduce index disk size? > Your inputs are much appreciated. > > Thanks, > Parth Gandhi > > -- > 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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/e343c173-da25-4281-8909-cea62cfdf6f3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e343c173-da25-4281-8909-cea62cfdf6f3%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/e343c173-da25-4281-8909-cea62cfdf6f3%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e343c173-da25-4281-8909-cea62cfdf6f3%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGvF%2BnExCR-%3DCr5Z1zdMQdMvaNbNw3q44Gg2\_sZTZgJQA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGvF%2BnExCR-%3DCr5Z1zdMQdMvaNbNw3q44Gg2_sZTZgJQA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:55am UTC](https://discuss.elastic.co/t/reduce-disk-space-requirements/20314/3 "2017-07-06T00:55:22Z")