We are thinking of eliminating path from index file, instead of replacing it. We need to further see if it is feasible to do so. I am looking into it. @Aravinda Vishwanathapura Krishna Murthy <avish...@redhat.com> @Kotresh Hiremath Ravishankar <khire...@redhat.com> Any pointers on this?
Regards, Shwetha On Mon, Sep 23, 2019 at 5:53 PM RAFI KC <rkavu...@redhat.com> wrote: > > 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 difficult. > > Rafi > > Are there any other general concerns regarding the same? > > Regards, > Shwetha > >
_______________________________________________ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/118564314 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/118564314 Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
