# 39m tweets on two nodes requires 11tb on S3?

**URL:** <https://discuss.elastic.co/t/39m-tweets-on-two-nodes-requires-11tb-on-s3/3628>\
**Category:** Elasticsearch\
**Created:** [December 4, 2010, 9:23pm UTC](https://discuss.elastic.co/t/39m-tweets-on-two-nodes-requires-11tb-on-s3/3628 "2010-12-04T21:23:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kenneth\_Loafman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman/32/2224_2.png) [@Kenneth\_Loafman](https://discuss.elastic.co/u/Kenneth_Loafman)\
**Post date:** [December 4, 2010, 9:23pm UTC](https://discuss.elastic.co/t/39m-tweets-on-two-nodes-requires-11tb-on-s3/3628/1 "2010-12-04T21:23:01Z")

</div>

[may be a dupe --- I sent from the wrong address originally]

Hi,

ES 0.11.0-SNAPSHOT has been running solid for a couple of months with an S3  
Gateway, but there's a serious problem. Status shows that there are 39m  
docs with a store size of 50.5 GB, see [https://gist.github.com/728313](https://gist.github.com/728313)  
. An 'ls' of the contents of the nodes shows thousands of '\_\_\*.partNN'  
files, some dated a couple of months ago. A 'du' of the indices/twitter  
directory (2 nodes) shows 11 TB, quite a bit of waste space!

What's the best way to compress and clean up this mess? Are old part files  
eligible for deletion? How do I keep this from happening again?

...Thanks,  
...Ken

---

<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, 4:15am UTC](https://discuss.elastic.co/t/39m-tweets-on-two-nodes-requires-11tb-on-s3/3628/2 "2017-07-06T04:15:43Z")

</div>