# Merges taking lots of space **URL:** \ **Category:** Elasticsearch\ **Created:** [April 26, 2018, 12:55pm UTC](https://discuss.elastic.co/t/merges-taking-lots-of-space/129671 "2018-04-26T12:55:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Thomas\_Deweer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomas_deweer/32/36138_2.png) [@Thomas\_Deweer](https://discuss.elastic.co/u/Thomas_Deweer)\ **Post date:** [April 26, 2018, 12:55pm UTC](https://discuss.elastic.co/t/merges-taking-lots-of-space/129671/1 "2018-04-26T12:55:11Z")
Hello, I'll try to briefly explain the situation: We have a record which we update once, so we have lots of deleted documents to be left out during merges, however, after a million documents, we perform a rollover, which makes the first index "locked", there will no longer be updates or writes to this index. However, despite a document not being huge, a million documents take up to 70gb, which made me suspicious. After looking up the stats of the index, it turns out about 35gb(total\_size\_in\_bytes) of data is located in "merges", which i assume is because we update every document once. The index only indicates "19456" deleted documents, which i consider rather weird regarding the merge size. Am I interpreting the statistics wrong or is there something I am doing wrong? Is there a way to reduce the merge size? Extra info: My index has 52 segments, would it be intresting to merge it to 1segment or would this be too much data for 1segment? I assume this would be no issue since it will be no longer updated? Any advice/help is welcome Kind regards, ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 24, 2018, 12:55pm UTC](https://discuss.elastic.co/t/merges-taking-lots-of-space/129671/2 "2018-05-24T12:55:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.