<div dir="ltr">Hi Aravinda,<br><br>Thanks for the update. I will get back to you in case of any queries.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 24, 2019 at 8:20 AM Aravinda Vishwanathapura Krishna Murthy <<a href="mailto:avishwan@redhat.com">avishwan@redhat.com</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 dir="ltr"><div>Hi Shwetha,</div><div><br></div><div>Good to see this bug is picked up.</div><div><br></div><div>You are right, and the fix should be to remove the path from HTIME file. RFE is already available here <a href="https://github.com/gluster/glusterfs/issues/76" target="_blank">https://github.com/gluster/glusterfs/issues/76</a></div><div><br></div><div>There is one more RFE about optimizing Changelogs storage. Currently, all changelogs are stored in a single directory, so this needs to be changed. This affects the above RFE, instead of storing a complete changelog path in HTIME file store with the prefix used in this RFE.</div><div><br></div><div><a href="https://github.com/gluster/glusterfs/issues/154" target="_blank">https://github.com/gluster/glusterfs/issues/154</a></div><div><br></div><div>These two RFE's to be worked together.</div><div><br></div><div>One major issue with format change is to handle the upgrades. Workaround script to be used to upgrade existing HTIME file and new directory structure of Changelog files.</div><div><br></div><div>Let me know if you have any questions.<br></div><div><br> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 23, 2019 at 4:14 PM Shwetha Acharya <<a href="mailto:sacharya@redhat.com" target="_blank">sacharya@redhat.com</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 dir="ltr">Hi All,<br>I am planning to work on <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1238699" target="_blank">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>Are there any other general concerns regarding the same?<br><br>Regards,<br>Shwetha<br></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail-m_491807065904668277gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>regards<br></div>Aravinda VK<br></div></div></div></div></div></div>
</blockquote></div>