Hi Scott, Thanks for replying.
After this problem, I've been faced with a huge amount of disk consumption regarding the aae folder (It's now in the order of the 100G). Indeed, I've been talking with your Brian Sparrow and he advised me to remove the anti antropy folder contents. Before that I'm going to attach to the riak process and stop the aae. After that I'll restart all the nodes one by one, removing the anti antropy contents in between. I should have done this by the time I've updated to 1.4.8, but unfortunately the message only appeared on the release notes after I've started the upgrade process... Best regards! On 6 March 2014 03:08, Scott Lystig Fritchie <fritc...@snookles.com> wrote: > Edgar Veiga <edgarmve...@gmail.com> wrote: > > ev> Is this normal? > > Yes. One or more of your vnodes can't keep up with the workload > generated by AAE repair .... or a vnode can't keep up for another > reason, and AAE repair shouldn't actively make things worse. > > The logging is done by: > > > https://github.com/basho/riak_kv/blob/1.4/src/riak_kv_entropy_manager.erl#L821 > > -Scott >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
