# Found existence of deleted and expired records in Aerospike!

**URL:** <https://discuss.aerospike.com/t/found-existence-of-deleted-and-expired-records-in-aerospike/1486>\
**Category:** Deletion\
**Tags:** deletion, durable-deletion\
**Created:** [July 14, 2015, 6:19am UTC](https://discuss.aerospike.com/t/found-existence-of-deleted-and-expired-records-in-aerospike/1486 "2015-07-14T06:19:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lucien](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/lucien/32/2065_2.png) [@lucien](https://discuss.aerospike.com/u/lucien)\
**Post date:** [July 17, 2015, 12:25am UTC](https://discuss.aerospike.com/t/found-existence-of-deleted-and-expired-records-in-aerospike/1486/2 "2015-07-17T00:25:01Z")

</div>

Deletes will remove the reference in memory but actual record will still exist on disk until it is overwritten. a cold start ( restart on the community edition) will force index to be rebuilt from disk.

Please see the following:

> [@How to ensure that deleted data from set does not come back?](https://discuss.aerospike.com/t/how-to-ensure-that-deleted-data-from-set-does-not-come-back/1306):
>
> Hello. After restart of the server, ‘zombie-records’ could appear due to the fact that we’ve deleted the whole set for example. How could we figure out if all of the records that are scheduled for deletion are erased from the SSD? Aerospike 3.3.21

If you have a cluster of nodes with at least replication factor\>=2 you may be able to use this option to ensure that the restarted node is re-indexed from its peer after data is replicated.

[http://www.aerospike.com/docs/reference/configuration/#cold-start-empty](http://www.aerospike.com/docs/reference/configuration/#cold-start-empty)

---

_[View the full topic](https://discuss.aerospike.com/t/found-existence-of-deleted-and-expired-records-in-aerospike/1486)._