# Old Data Not Being Purged

**URL:** <https://discuss.elastic.co/t/old-data-not-being-purged/155718>\
**Category:** Elasticsearch\
**Created:** [November 7, 2018, 12:43pm UTC](https://discuss.elastic.co/t/old-data-not-being-purged/155718 "2018-11-07T12:43:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SamJWeissman](https://avatars.discourse-cdn.com/v4/letter/s/a183cd/32.png) [@SamJWeissman](https://discuss.elastic.co/u/SamJWeissman)\
**Post date:** [November 7, 2018, 12:43pm UTC](https://discuss.elastic.co/t/old-data-not-being-purged/155718/1 "2018-11-07T12:43:35Z")

</div>

Hello,

I am currently using ElasticCloud and have been attempting to modify my documents by performing the same bulk index calls I used to insert them the first go around.

I was under the impression that these index calls should just update documents with the same \_ids ( which it appears to be doing ).

Unfortunately, where as my memory pressure/disk usage would previously drop (around 75%), it is now just continuously going up (up to 93% right now).

I do not have duplicate searchable documents, and I do see that the version of the documents I've touched have had their version numbers increased. So it seems like the "index" operations are correctly performing "updates".

However, being that memory/disk usage just keeps going up, my only explanation is that the older documents are not being purged from memory/disk.

Not really sure where to go from here outside of deleting the entire index and actually starting from scratch.

Any help would be greatly appreciated

---

<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:** [December 5, 2018, 12:43pm UTC](https://discuss.elastic.co/t/old-data-not-being-purged/155718/2 "2018-12-05T12:43:52Z")

</div>

Closed on December 5, 2018, 12:43pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
