[Gluster-users] Unavailability during self-heal for large volumes
Pranith Kumar Karampuri
pkarampu at redhat.com
Tue Jun 3 00:42:36 UTC 2014
----- Original Message -----
> From: "Laurent Chouinard" <laurent.chouinard at ubisoft.com>
> To: "Pranith Kumar Karampuri" <pkarampu at redhat.com>
> Cc: gluster-users at gluster.org
> Sent: Tuesday, June 3, 2014 12:56:40 AM
> Subject: RE: [Gluster-users] Unavailability during self-heal for large volumes
> > Laurent,
> > This has been improved significantly in afr-v2 (enhanced version of
> > replication
> > translator in gluster) which will be released with 3.6 I believe. The issue
> > happens
> > because of the directory self-heal in the older versions. In the new
> > version per file
> > healing in a directory is performed instead of Full directory heal at-once
> > which was
> > creating a lot of traffic. Unfortunately This is too big a change to
> > backport to older
> > releases :-(.
> > Pranith
> Hi Pranith,
> Thank you for this information.
> Do you think there is a way to limit/throttle the current directory self-heal
> then? I don't mind if it takes a long time.
> Alternatively, is there a way to completely disable the complete healing
> system? I would consider running a manual healing operation by STAT'ing
> every file, which would allow me to throttle the speed to a more manageable
gluster volume set <volume-name> cluster.self-heal-daemon off would disable glustershd performing automatic healing.
> Laurent Chouinard
More information about the Gluster-users