[Gluster-users] Geo Replication Hooks
yknev.shankar at gmail.com
Tue Nov 26 05:42:32 UTC 2013
You could implement this without touching Geo-Replication code. Gluster now
has the changelog translator (journaling mechanism) which records changes
made to the filesystem (on each brick). Journals can be consumed using the
changelog consumer library (libgfchangelog). Geo-Replication is just one
such consumer of the changelogs (earlier the change detection mechanism
used to be a filesystem crawl based on xtime).
Thinking from hook-scripts POV, you would even invoke them from
libgfchangelog -- which gets notified by the changelog translator after a
certain time interval. The granularity here would be a bunch of files
(GFIDs actually, not file names) instead of per file basis. The library has
APIs to mark changelogs as processed, which would be used to invoke post
replication hooks (but this is only on source, not on destination).
Let me know what you think of the above approaches.
On Tue, Nov 26, 2013 at 3:13 AM, Fred van Zwieten
<fvzwieten at vxcompany.com>wrote:
> I have created a proposal for the implementation of Geo Replication Hooks.
> See here:
> Any comments, thoughts, etc would be great.
> Gluster-users mailing list
> Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users