Memory-backend TTL

Lucas Grijander lucasgrinjander69 at
Fri Oct 3 14:32:17 EDT 2014


I have a memory backend in production with Riak 2.0.1, 4 servers and 256
vnodes. The servers have the same date and time.

I have seen an odd performance with the ttl.

This is the config:


For example, see this GET response in one of the riak servers:

< HTTP/1.1 200 OK
< X-Riak-Vclock: a85hYGBgzGDKBVIc4otdfgR/7bfIYEpkzGNlKI1efJYvCwA=
< Vary: Accept-Encoding
* Server MochiWeb/1.1 WebMachine/1.10.5 (jokes are better explained) is not
< Server: MochiWeb/1.1 WebMachine/1.10.5 (jokes are better explained)
< Link: </riak/ttl_stg>; rel="up"
< Last-Modified: Fri, 03 Oct 2014 17:40:05 GMT
< ETag: "3c8bGoifWcOCSVn0otD5nI"
< Date: Fri, 03 Oct 2014 17:47:50 GMT
< Content-Type: application/json
< Content-Length: 17

If the TTL is 90 seconds, Why the GET doesn't return "not found" if the
difference between "Last-Modified" and "Date" (of the curl request) is
greater than the TTL?

Thanks in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the riak-users mailing list