<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 9/23/19 4:13 PM, Shwetha Acharya
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAERh03prk2SnXU=gb=YSJ6z-D2Jc1povyM8Wai7PR4bNiCSLDg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi All,<br>
I am planning to work on <a
href="https://bugzilla.redhat.com/show_bug.cgi?id=1238699"
moz-do-not-send="true">this</a> bugzilla issue. <br>
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.<br>
<br>
I have some doubts regarding the same.<br>
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? <br>
Is it important to have paths inside index file? Can we
eliminate the paths inside them?<br>
Is there any concerns from snapshot side?<br>
</div>
</blockquote>
<p>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.</p>
<p>Rafi</p>
<blockquote type="cite"
cite="mid:CAERh03prk2SnXU=gb=YSJ6z-D2Jc1povyM8Wai7PR4bNiCSLDg@mail.gmail.com">
<div dir="ltr">Are there any other general concerns regarding the
same?<br>
<br>
Regards,<br>
Shwetha<br>
</div>
</blockquote>
</body>
</html>