Memory-backend TTL

Luke Bakken lbakken at basho.com
Tue Dec 16 15:51:50 EST 2014


Hi Juan,

Please see: https://github.com/basho/riak_kv/issues/1064

I have also forwarded this on internally.

--
Luke Bakken
Engineer / CSE
lbakken at basho.com


On Tue, Dec 16, 2014 at 10:52 AM, Juan Luis Francés
<jl.frances.j at conekia.es> wrote:
> Hello.
>
> Do you have any update about this issue? I am affected by the same memory leak. Sadly, this problem does the Riak memory backend useless in production.
>
> You can reproduce it with this dirty script (be careful, it is resource intensive):
>
> https://gist.github.com/indpnday/76d99c5852e0100c5a04
>
> - 1 Riak node 2.0.1.
> - riak.conf:
>
> buckets.default.n_val = 1
> buckets.default.last_write_wins = true
> buckets.default.r = 1
> buckets.default.w = 1
> multi_backend.memory.storage_backend = memory
> multi_backend.memory.memory_backend.ttl = 90s
> multi_backend.memory.memory_backend.max_memory_per_vnode = 250MB
>
>
> # curl http://127.0.0.1:8098/buckets/memory/props
> {"props":{"allow_mult":false,"backend”:"memory","basic_quorum":false,"big_vclock":50,"chash_keyfun":{"mod":"riak_core_util","fun":"chash_std_keyfun"},"dvv_enabled":false,"dw":"quorum","last_write_wins":true,"linkfun":{"mod":"riak_kv_wm_link_walker","fun":"mapreduce_linkfun"},"n_val":1,"name”:"memory","notfound_ok":true,"old_vclock":86400,"postcommit":[],"pr":0,"precommit":[],"pw":0,"r":1,"rw":"quorum","small_vclock":50,"w":1,"young_vclock":20}}
>
>
> Is there any bug report opened in github where to follow this issue?
>
> Best regards,
> Juan Luis Francés




More information about the riak-users mailing list