<div dir="ltr">Hi Felix,<br><br><div>Index here is stime or sync time. Once we set sync time to 0, crawl happens from the beginning, till stime < xtime. (xtime is last modified time of file or directory on master)<br>We can achieve it using following steps:<br><pre class="gmail-bz_comment_text" id="gmail-comment_text_38" style="white-space:pre-wrap;margin:1em;padding-bottom:1em"><font color="#000000" style="background-color:rgb(243,243,243)"># gluster volume geo-replication master-vol slave-ip::slave-vol stop
# gluster volume geo-replication master-vol slave-ip::slave-vol delete reset-sync-time
# gluster vol geo-rep master-vol slave-ip::slave-vol create push-pem
# gluster volume geo-replication master-vol slave-ip::slave-vol start
</font></pre></div><div>The above procedure is resource intensive and time consuming, and not recommended for huge data set.<br><br>One more alternative would be to triggering sync on indivisual files,<br># setfattr -n glusterfs.geo-rep.trigger-sync -v "1" <file-path><br><br></div><div>Regards,<span style="background-color:transparent;color:inherit;font-family:Consolas,Monaco,"Andale Mono",monospace;font-size:inherit;white-space:pre-wrap"></span></div><div>Shwetha<br><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 22, 2020 at 1:02 PM Felix Kölzow <<a href="mailto:felix.koelzow@gmx.de">felix.koelzow@gmx.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Dear Shwetha,</p>
<p><br>
</p>
<p>thank you very much for your immediate response. <br>
</p>
<p>It turns out we have rsync 3.1.2, so this sould be fine. <br>
</p>
<p>Actually, geo-rep is in xsync mode, but just due to <br>
</p>
<p>the fact that I deleted the geo-replication and used the
reset-sync-time option.<br>
</p>
<p>
</p><blockquote type="cite"><span style="background-color:rgb(255,255,255)"><br>
If you are looking to still resync, you can go for the option
of erasing the index and restarting geo-replication.</span></blockquote>
<p></p>
<p>Ok, this is what I am looking for. How to do it?</p>
<p><br>
</p>
<p>Regards,</p>
<p>Felix<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Actually, we are running rsync <br>
</p>
<div>On 22/06/2020 09:24, Shwetha Acharya
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">Hi Felix,<br>
Find the reply inline below.</div>
<div dir="ltr"><br>
</div>
<div>Regards,<br>
Shwetha</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Jun 22, 2020 at
12:19 PM Felix Kölzow <<a href="mailto:felix.koelzow@gmx.de" target="_blank">felix.koelzow@gmx.de</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> Would it be possible
for you to provide more specifics about the<br>
> issues you see and the release in which these are seen?<br>
<br>
Some files on the slave side still exist, while they are
deleted on the<br>
master side many month ago. Due to<br>
<br>
</blockquote>
<div>one possibility of deletes or renames not being synced
is, when the geo-rep is in hybrid crawl(or in other words
Xsync)</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
another issue, I would like to initiate a re-sync just to
assure that<br>
master and slave are identical.<br>
<br>
How to achieve this and how to monitor that this was
pocedure is ongoing<br>
and successful?<br>
<br>
</blockquote>
<div><span style="background-color:rgb(255,255,255)">Firstly
you can verify if you have installed the required version
of rsync, Geo-replication requires rsync v3.0.0. or higher
on the host and remote machines. <br>
<br>
If you are looking to still resync, you can go for the
option of erasing the index and restarting
geo-replication.<br>
<br>
<br>
</span></div>
<div><span style="background-color:rgb(255,255,255)"><br>
</span></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Regards,<br>
<br>
Felix<span> </span></blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
________<br>
<br>
<br>
<br>
Community Meeting Calendar:<br>
<br>
Schedule -<br>
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer" target="_blank">https://bluejeans.com/441850968</a><br>
<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
________<br>
<br>
<br>
<br>
Community Meeting Calendar:<br>
<br>
Schedule -<br>
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer" target="_blank">https://bluejeans.com/441850968</a><br>
<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>