[Gluster-devel] Persistent AFR changelog attributes

Ravishankar N ravishankar at redhat.com
Wed Feb 12 04:33:32 UTC 2014


As you might perhaps be aware, AFR translator currently uses the client 
translator names  as the name of it's changelog extended attributes.

i)This can be a problem when a remove-brick operation is performed when 
there are pending heals happening because remove-brick causes a graph 
change wherein the client translator names become different.

ii) Also, for gluster snapshot volumes to work correctly, there needs to 
be a persistent mapping of AFR changelog attributes to the bricks.

After some internal discussions, we have come up with a new naming 
mechanism that ensures backward compatibility. Details on the 
aforementioned problems and the proposed solution are detailed in a 
feature page [1] for GlusterFS 3.6.
Please feel free to go through it and give your comments/ critiques.

Thanks and regards,


More information about the Gluster-devel mailing list