Hi Edgar, please note that I’ve run into the same problem. And I did what you’re describing: restarting the nodes one by one and removing the AAE folders. However I am strongly suspecting that this didn’t solve it completely for me since a few nodes kept thrashing the disk continuously. My gut feeling says this is because the AAE starts immediately when the node is started and some of the other nodes then still have the incorrect/faulty AAE data, immediately triggering repairs or something.
So I stopped AAE on all nodes (with riak attach), removed the AAE folders on all the nodes. And then restarted them one-by-one, so they all started with a clean AAE state. Then about a day later the cluster was finally in a normal state. Regards, Timo p.s. of course I can be wrong and maybe the I/O was caused by something else. > Message: 5 > Date: Thu, 6 Mar 2014 10:15:55 +0000 > From: Edgar Veiga <[email protected]> > To: Scott Lystig Fritchie <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: Update to 1.4.8 > Message-ID: > <CAM-EGEqp=3eqi6r2zji9yryactgsz-1btwzqz1h_ofd-xvd...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > 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… >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
