riak_kv_cache_backend config questions
t.bussieres at gmail.com
Tue Aug 23 10:38:35 EDT 2011
So, if I understood well.
with a config like this :
*If I put a key at time 0, and access it will disappear after 60 second.
If I put a key at time 0, and access it at time 50, it will disappear at
If I put a key at time 0, and access it every 15 seconds, it will disappear
after 300 seconds.
I'm I right?
On Tue, Aug 23, 2011 at 10:22 AM, Kelly McLaughlin <kelly at basho.com> wrote:
> riak_kv_cache_backend_ttl is the amount of time to extend an object's lease
> or lifespan when accessed whereas *riak_kv_cache_backend_max_ttl is the
> amount of time after which no further extensions should be granted. *
> On Aug 23, 2011, at 7:49 AM, Tony Bussieres wrote:
> Hi all,
> Could someone explain with an example what's the difference between :
> Does the value of riak_kv_backend_max_ttl is also in seconds?
> Here's a snippet from the documentation found at
> - *riak_kv_cache_backend*
> A backend that behaves as an LRU-with-timed-expiry cache
> - *riak_kv_cache_backend_memory*
> Maximum amount of memory to allocate, in megabytes (default: “100”)
> - *riak_kv_cache_backend_ttl*
> Amount by which to extend an object’s expiry lease on each access,
> in seconds (default: “600”)
> - *riak_kv_cache_backend_max_ttl*
> Maximum allowed lease time (default: “3600”)
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users