# Durability issue: lost set after 3-4 days

**URL:** <https://discuss.aerospike.com/t/durability-issue-lost-set-after-3-4-days/416>\
**Category:** General Discussion\
**Created:** [September 19, 2014, 5:23am UTC](https://discuss.aerospike.com/t/durability-issue-lost-set-after-3-4-days/416 "2014-09-19T05:23:44Z")\
**Posts on this page:** 1\
**Showing post:** 17

<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:** [June 30, 2015, 6:28pm UTC](https://discuss.aerospike.com/t/durability-issue-lost-set-after-3-4-days/416/17 "2015-06-30T18:28:44Z")

</div>

Default-ttl is set to 0 by default if it not harcoded in the config file. Which means that records are set to not expire unless overwritten by the application.

Its not really a problem, but more of how aerospike handles deletes to ensure high performance. For more details please read [Deletes More info…](https://discuss.aerospike.com/t/how-to-ensure-that-deleted-data-from-set-does-not-come-back/1306)

In your particular case you should be able to use Method#4 to clean old data and ensure that your test sets does not return. Please see: [https://discuss.aerospike.com/t/bin-names-deletion/731](https://discuss.aerospike.com/t/bin-names-deletion/731)

You can also use Method#1 by setting a default-ttl \> 0 and wait for that data to expire prior to restarting the node. This method assumes that record was not initially set to a default-ttl of 0.

---

_[View the full topic](https://discuss.aerospike.com/t/durability-issue-lost-set-after-3-4-days/416)._
