[Gluster-devel] Persistent AFR changelog attributes

Anand Avati avati at gluster.org
Wed Feb 12 05:00:29 UTC 2014

We had earlier discussed a solution for this (sometime last year) by making
volgen remember xlator names and not reassign them. Copying KP with who I
had discussed this to quite a level of detail. Have you guys spoken about
this? IIRC the solution KP and I discussed was more generic and could also
support retaining user made changes/customizations to the volfiles.


On Tue, Feb 11, 2014 at 8:33 PM, Ravishankar N <ravishankar at redhat.com>wrote:

> Hello,
> 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,
> Ravi
> [1] https://www.gluster.org/community/documentation/index.
> php/Features/persistent-AFR-changelog-xattributes
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> https://lists.nongnu.org/mailman/listinfo/gluster-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20140211/88ee5dea/attachment-0001.html>

More information about the Gluster-devel mailing list