|
Sounds nice. And then the question is
what happens when that limit is reached on a node?
On 10/18/2013 02:21 PM, Matthew Von-Maszewski wrote:
The user has the option of setting a default memory limit in the
app.config / riak.conf file (either absolute number or percentage
of total system memory). There is a default percentage (which I
am still adjusting) if the user takes no action.
The single memory value is then dynamically partitioned to
each Riak vnode (and AAE vnodes) as the server takes on more or
fewer vnodes throughout normal operations and node failures.
There is no human interaction required once the memory limit
is established.
Matthew
Is it smart enough to manage itself?
Or does it require human babysitting?
Sent from my
Verizon Wireless 4G LTE Smartphone
-------- Original message --------
From: Matthew Von-Maszewski < matth...@basho.com>
Date: 10/18/2013 1:48 PM (GMT-05:00)
To: Dave Martorana < d...@flyclops.com>
Cc: darren < dar...@ontrenet.com>, riak-users@lists.basho.com
Subject: Re: Riak consumes too much memory
Dave,
flexcache will be a new feature in Riak 2.0. There
are some subscribers to this mailing list that like to
download and try things early. I was directing those
subscribers to the GitHub branch that contains the
work-in-progress code.
flexcache is a new method for sizing / accounting the
memory used by leveldb. It replaces the current method
completely. flexcache is therefore not an option, but
an upgrade to the existing logic.
Matthew
Matthew,
For we who don't quite understand, can you
explain - does this mean mv-flexcache is a
feature that just comes with 2.0, or is it
something that will need to be turned on, etc?
Thanks!
Dave
|
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
