The marker translator takes care of the "upward recursive" xtime setxattr operation whenever a fop triggers a change for file/directory in the gluster volume.<div><br></div><div>So, yes; marking is close to real-time.<br>
<div><br></div><div>Thanks,</div><div>-Venky<br><br><div class="gmail_quote">On Fri, Jun 1, 2012 at 12:57 PM, Gandalf Corvotempesta <span dir="ltr"><<a href="mailto:gandalf.corvotempesta@gmail.com" target="_blank">gandalf.corvotempesta@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div class="im">2012/6/1 Venky Shankar <span dir="ltr"><<a href="mailto:yknev.shankar@gmail.com" target="_blank">yknev.shankar@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Whenever an entity is the master gluster volume is changed (writes) the marker xlator (feature/marker) updates the xtime extended attribute for that particular file and propagates it up the directory hierarchy. This by looking at the top level directory (xtime-master > xtime-slave) gsyncd knows whether there some change in the tree. Gsyncd then recursively walks the tree (only entering sub-directories that satisfy xtime(M) > xtime(S)) to get a list of files that have xtime differences b/w master and slave.<br>
<br></blockquote></div><div>Is this in real time? </div></div><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Astalavista Baby!!!<br>
</div></div>