1.4.8, memory_backend max_memory not honored?

Luke Bakken lbakken at basho.com
Tue Jun 24 12:15:17 EDT 2014

Hi Allen,

There were some fixes to the memory backend in 1.4.9:

Could you please provide your app.config file? I'd like to check it and
test out your scenario locally.

Luke Bakken
lbakken at basho.com

On Tue, Jun 24, 2014 at 8:59 AM, Allen Landsidel <landsidel.allen at gmail.com>

> Test cluster with 2 machines running 1.4.8 with the memory backend.
> app_config has ring_creation_size 64, max_memory 4.  If I understand the
> documentation correctly this should result in a maximum memory footprint
> (minus overhead) of 256M.  Each node has 2G RAM, 2G of swap.  After running
> for a while constantly adding data, without ever explicitly removing any,
> the memory footprint outstrips physical ram and will eventually consume all
> available swap space and be killed.
> Is this a known issue in 1.4.8 that's fixed in 1.4.9, or is there other
> configuration settings that need adjusted to reduce the footprint?
> Initially I had set it up to top out at 1GB but when it started exhausting
> swap, I progressively reduced max_memory until I arrived where I am now,
> with no difference at all.
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20140624/7cb73762/attachment.html>

More information about the riak-users mailing list