[Gluster-users] Reliable Geo-Replication

[Shwetha Acharya]

Deleting geo-rep session with reset-sync-time, makes sure that sync
time(stime) is reset. Sync time is last time when the sync happened from
master to slave.

Regards,
Shwetha

On Mon, Jun 22, 2020 at 2:42 PM Shwetha Acharya <sacharya at redhat.com> wrote:

> Hi Felix,
>
> 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)
> We can achieve it using following steps:
>
> # 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
>
> The above procedure is resource intensive and time consuming, and not
> recommended for huge data set.
>
> One more alternative would be to triggering sync on indivisual files,
> # setfattr -n glusterfs.geo-rep.trigger-sync -v "1" <file-path>
>
> Regards,
> Shwetha
>
>
>
> On Mon, Jun 22, 2020 at 1:02 PM Felix Kölzow <felix.koelzow at gmx.de> wrote:
>
>> Dear Shwetha,
>>
>>
>> thank you very much for your immediate response.
>>
>> It turns out we have rsync 3.1.2, so this sould be fine.
>>
>> Actually, geo-rep is in xsync mode, but just due to
>>
>> the fact that I deleted the geo-replication and used the reset-sync-time
>> option.
>>
>>
>> If you are looking to still resync, you can go for the option of erasing
>> the index and restarting geo-replication.
>>
>> Ok, this is what I am looking for. How to do it?
>>
>>
>> Regards,
>>
>> Felix
>>
>>
>>
>> Actually, we are running rsync
>> On 22/06/2020 09:24, Shwetha Acharya wrote:
>>
>> Hi Felix,
>> Find the reply inline below.
>>
>> Regards,
>> Shwetha
>>
>> On Mon, Jun 22, 2020 at 12:19 PM Felix Kölzow <felix.koelzow at gmx.de>
>> wrote:
>>
>>> > Would it be possible for you to provide more specifics about the
>>> > issues you see and the release in which these are seen?
>>>
>>> Some files on the slave side still exist, while they are deleted on the
>>> master side many month ago. Due to
>>>
>>> one possibility of deletes or renames not being synced is, when the
>> geo-rep is in hybrid crawl(or in other words Xsync)
>>
>>> another issue, I would like to initiate a re-sync just to assure that
>>> master and slave are identical.
>>>
>>> How to achieve this and how to monitor that this was pocedure is ongoing
>>> and successful?
>>>
>>> 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.
>>
>> If you are looking to still resync, you can go for the option of erasing
>> the index and restarting geo-replication.
>>
>>
>>
>>
>>> Regards,
>>>
>>> Felix
>>
>>
>>>
>>> ________
>>>
>>>
>>>
>>> Community Meeting Calendar:
>>>
>>> Schedule -
>>> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
>>> Bridge: https://bluejeans.com/441850968
>>>
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org
>>> https://lists.gluster.org/mailman/listinfo/gluster-users
>>>
>>> ________
>>
>>
>>
>> Community Meeting Calendar:
>>
>> Schedule -
>> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
>> Bridge: https://bluejeans.com/441850968
>>
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> https://lists.gluster.org/mailman/listinfo/gluster-users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200622/74ff8d5b/attachment.html>