Hi,
In our production system, we notice that merges are not taking place. We
have noticed, however, that when we restart riak (via a 'riak stop' then a
'riak start'), then the merges are triggered and our disk usage goes way
day (which is what we want). We use bitcask.
Why does this happen on a restart only and not at other times, even though
we have set our merge_window config setting to 'always'?
I'm assuming our config values are correct as the restart considers the
thresholds met to go ahead with a merge.
Also: Are there any tools out there that I can run on my data directory
that will tell me the size of the dead byte ratios? Would be nice to see
what the dead byte 'state' of my data dir is in so I can tell whether
indeed merge conditions are met.
Our bit cask configs are as follows in app.config:
{bitcask, [
{data_root, "/var/lib/riak/bitcask"},
{dead_bytes_merge_trigger, 268435456},
{dead_bytes_threshold, 134217728},
{expiry_secs, 3888000},
{frag_merge_trigger, 40},
{frag_threshold, 20},
{merge_window, always},
{small_file_threshold, 10485760},
{sync_strategy, none}
]},
Thanks!
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
