# Conflict-resolution-policy=ttl

**URL:** <https://discuss.aerospike.com/t/conflict-resolution-policy-ttl/2626>\
**Category:** Operations\
**Created:** [March 11, 2016, 9:14am UTC](https://discuss.aerospike.com/t/conflict-resolution-policy-ttl/2626 "2016-03-11T09:14:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gerhard](https://avatars.discourse-cdn.com/v4/letter/g/b5e925/32.png) [@gerhard](https://discuss.aerospike.com/u/gerhard)\
**Post date:** [March 11, 2016, 9:14am UTC](https://discuss.aerospike.com/t/conflict-resolution-policy-ttl/2626/1 "2016-03-11T09:14:49Z")

</div>

Hello,

I have counters stored in Aerospike that are updated often and old values return after restart because of generation wrap. From what I’ve read in the forum, setting conflict-resolution-policy to ttl can help, as this will ensure I’ll always get the latest data on conflict resolution. However what are the risks / downside of using this?