[Gluster-devel] Geo-rep start after snapshot restore makes the geo-rep faulty

RAFI KC rkavunga at redhat.com
Mon Sep 23 12:23:35 UTC 2019

On 9/23/19 4:13 PM, Shwetha Acharya wrote:
> Hi All,
> I am planning to work on this 
> <https://bugzilla.redhat.com/show_bug.cgi?id=1238699> bugzilla issue.
> Here, when we restore the snapshots, and start the geo-replication 
> session, we see that the geo-replication goes faulty. It is mainly 
> because, the brick path of original session and the session after 
> snapshot restore will be different. There is a proposed work around 
> for this issue, according to which we replace the old brick path with 
> new brick path inside the index file HTIME.xxxxxxxxxx, which basically 
> solves the issue.
> I have some doubts regarding the same.
> We are going with the work around from a long time. Are there any 
> limitations stopping us from implementing solution for this, which I 
> am currently unaware of?
> Is it important to have paths inside index file? Can we eliminate the 
> paths inside them?
> Is there any concerns from snapshot side?

Can you please explain how we are planning to replace the path in the 
index file. Did we finalized the method? The problem here is that any 
time consuming operation within the glusterd transaction could be a 


> Are there any other general concerns regarding the same?
> Regards,
> Shwetha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20190923/5cc33de6/attachment.html>

More information about the Gluster-devel mailing list