To followup:
Since we use chef (configuration management), the riak configs are the same
across all our riak nodes (except for stuff like hostnames/IPs, etc.).
I ran riak_kv:repair and it looks like it had fixed the problem on node
004, but then a _different_ node (002) started to throw a bunch o
Johnny:
Something else to look for would be any errors in the console.log related to
Bitcask merging. It would be interesting to see if the unusual disk
utilization was related to a specific partition. If it is, you could consider
removing that particular partition and running riak_kv:repair
Hi Johnny. Make sure that the configuration on that node is not different
to the others. For example, it could be configured to never merge Bitcask
files, so that space could never be reclaimed.
http://docs.basho.com/riak/latest/ops/advanced/backends/bitcask/#Configuring-Bitcask
On Thu, May 14, 2
We have a 6-node test riak cluster. One of the nodes seems to be using far
more disk:
staging-riak001.pp /dev/sda3 15G 6.3G 7.2G 47% /
staging-riak002.pp /dev/sda3 15G 6.4G 7.1G 48% /
staging-riak003.pp /dev/sda3 15G 6.1G 7.5G 45% /
staging-riak004.pp
