Could you please attacj the brick logs and glustershd logs?
Also share the volume configuration please (`gluster volume info`).On Mon, Aug 15, 2016 at 12:19 PM, Lindsay Mathieson <lindsay.mathieson@xxxxxxxxx> wrote:
Moved to a new subject as its now an issue on our cluster.
As an experiment I killed glusterfsd on one node. System kept
chugging allong fine with no hiccups. I ran a few disk intensive VM's
on that node and others, no real slow down. Monitoring it with "heal
statistics heal-count'
heal-count got up to approx 2500 shards and restarted glusterfsd by
restarting the gluster-service (glusterd).
heal-count stopped rising, but what is concerning is that it doesn't
seem to be going back down. 45min later at its stable at 2439 files
needing healed and glusterfsd is thrashing the CPU's on that node
(1000%!)
The glfsheal log has no entries at all.
Previously (3.7.x) when I've done this test, heals kicked in very rapidly.
At three hours later, still no progress in heal at all. VM's on other
nodes getting occasional read timeouts.
heal-count = 2550, and not changing.
--
Lindsay
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
