No, no noticeable difference. Still very high, possibly higher than before. The system has come down to a crawl. It's difficult to even ssh or run any commands on the terminal. Do you make anything of the logs ? The brick log is just a giant alternating stream of those two lines I mentioned earlier.
On Thu, Aug 6, 2015 at 10:10 PM, Ravishankar N <ravishankar@xxxxxxxxxx> wrote:
On 08/07/2015 01:33 AM, Prasun Gera wrote:
I replaced the brick in a node in my 3x2 dist+repl volume (RHS 3). I'm seeing that the heal process, which should essentially be a dump from the working replica to the newly added one is taking exceptionally long. It has moved ~100 G over a day on a 1Gigabit network. The CPU usage on both the nodes of the replica has been pretty high.
Does setting `cluster.data-self-heal-algorithm` to full make a difference in the cpu usage?
I also think that nagios is making it worse. The heal is slow enough as it is, and nagios keeps triggering heal info, which I think never completes. I also see my logs filling up These are some of the log contents which I got by running tail on them:
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
