Hi Sam,
I think they are likely referring to the memory_ets Riak statistic.
This is just a straight export of erlang:memory(ets). [1], [2]
You're probably right that they're using LevelDB, given the data (and
presumably key) volumes they're talking about. However, LevelDB's
various types of cachi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've gone through the great post[1] by Meltwater and a couple of things
caught my eye.
One of which is "The only thing we noticed inside Riak, that correlated
to the elevated load, was that it dropped its internal caching
structures, the ETS tables
Hi,
I'm seeing strange things with bitcask expiration: When a new node joins
a Ring, it gets data from the other nodes to rebalance. It seems that
the starting date to count expiration of this data is the time when they
were copied to the new node, *not* the date they were originally created
Glad we got to the bottom of it.
You should probably look at updating your docs for Riak-CS and removing
stanchion 1.5 from the repo to avoid future confusion?
On Wed, 10 Jun 2015 at 00:46 Kota Uenishi wrote:
> I got it! Good catch, Chris.
>
> Toby, you should follow these instructions to get th
