[Gluster-users] Healing Delays
lindsay.mathieson at gmail.com
Sat Oct 1 14:48:22 UTC 2016
This was raised earlier but I don't believe it was ever resolved and it
is becoming a serious issue for me.
I'm doing rolling upgrades on our three node cluster (Replica 3,
Sharded, VM Workload).
I update one node, reboot it, wait for healing to complete, do the next one.
Only the heal count does not change, it just does not seem to start. It
can take hours before it shifts, but once it does, its quite rapid. Node
1 has restarted and the heal count has been static at 511 shards for 45
minutes now. Nodes 1 & 2 have low CPU load, node 3 has glusterfsd pegged
at 800% CPU.
This was *not* the case in earlier versions of gluster (3.7.11 I think),
healing would start almost right away. I think it started doing this
when the afr locking improvements where made.
I have experimented with full & diff heal modes, doesn't make any
Gluster Version 4.8.4
Volume Name: datastore4
Volume ID: 0ba131ef-311d-4bb1-be46-596e83b2f6ce
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
More information about the Gluster-users