<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Dear Shwetha,</p>
    <p><br>
    </p>
    <p>yes, I deleted the previous session including the
      [reset-sync-time] option.</p>
    <p>Actually, the geo-replication is in hybrid crawl and I executed
      the command <br>
    </p>
    <p>what we discussed yesterday. # setfattr ....</p>
    <p><br>
    </p>
    <p>So far, the files are still present on the slave side.</p>
    <p>You mentioned that renames and deletes are not going to be
      considered in hybrid crawl,</p>
    <p>the command setfattr... is actually not useful, since our
      geo-replication is still in hybrid crawl?</p>
    <p><br>
    </p>
    <p>You already asked which issues are we actually faced using
      geo-replication.</p>
    <p>For another volume, here is a snippet of the log-file:</p>
    <p>[2020-06-23 06:40:10.280570] E [repce(agent
      path2brick):121:worker] &lt;top&gt;: call failed: <br>
      Traceback (most recent call last):<br>
        File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line
      117, in worker<br>
          res = getattr(self.obj, rmeth)(*in_data[2:])<br>
        File
      "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line
      40, in register<br>
          return Changes.cl_register(cl_brick, cl_dir, cl_log, cl_level,
      retries)<br>
        File
      "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line
      46, in cl_register<br>
          cls.raise_changelog_err()<br>
        File
      "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line
      30, in raise_changelog_err<br>
          raise ChangelogException(errn, os.strerror(errn))<br>
      ChangelogException: [Errno 2] No such file or directory<br>
      [2020-06-23 06:40:10.281264] E [repce(worker
      path2brick):213:__call__] RepceClient: call failed   
      call=100462:139896734930752:1592894408.19    method=register   
      error=ChangelogException<br>
      [2020-06-23 06:40:10.281446] E [resource(worker
      path2brick):1286:service_loop] GLUSTER: Changelog register
      failed    error=[Errno 2] No such file or directory<br>
      [2020-06-23 06:40:10.283895] E [repce(agent
      path2brick):121:worker] &lt;top&gt;: call failed: <br>
      Traceback (most recent call last):<br>
        File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line
      117, in worker<br>
          res = getattr(self.obj, rmeth)(*in_data[2:])<br>
        File
      "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line
      40, in register<br>
          return Changes.cl_register(cl_brick, cl_dir, cl_log, cl_level,
      retries)<br>
        File
      "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line
      46, in cl_register<br>
          cls.raise_changelog_err()<br>
        File
      "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line
      30, in raise_changelog_err<br>
          raise ChangelogException(errn, os.strerror(errn))<br>
      ChangelogException: [Errno 2] No such file or directory<br>
      [2020-06-23 06:40:10.285129] E [repce(worker
      path2brick):213:__call__] RepceClient: call failed   
      call=100465:140153610073920:1592894408.19    method=register   
      error=ChangelogException<br>
      <br>
    </p>
    <p>Due to this issue, the geo-replication is going from passive to
      active to faulty to initialise and starts from the beginning, ....
      (endless loop) and no</p>
    <p>progress in synchronisation. <br>
    </p>
    <p>Regards,</p>
    <p>Felix</p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 22/06/2020 13:49, Shwetha Acharya
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAERh03o9h10B7cvR5mUrrCbNvB27TRiH12i3Ki0Hdbq_XYbGHw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Hi Felix,<br>
        <br>
        <div>Have you deleted the session with reset-sync-time and
          recreated the session?<br>
          <br>
          If yes, the crawling starts from beginning.</div>
        <div>Which happens in this way:<br>
          <br>
          It begins with hybrid crawl, as data is already in  master
          before re creating the geo-rep session. If geo-rep session is
          craeted before creating data on master, hybrid crawl does not
          occur. <b>Note</b>:  renames and deletes will not be synced
          in hybrid crawl. <br>
          <br>
          Then it gradually changes to history crawl and changelog
          crawl.<br>
          <br>
          You can wait for sync to complete by setting a checkpoint,
          need not try <span style="color:rgb(80,0,80)"># setfattr -n
            glusterfs.geo-rep.trigger-sync -v "1" &lt;file-path&gt; </span><br>
          reset-sync-time will take considerable time to finish syncing,
          as I stated earlier, it is time consuming one.<br>
          <br>
          Modes does not affect <span style="color:rgb(80,0,80)">#
            setfattr -n glusterfs.geo-rep.trigger-sync -v "1"
            &lt;file-path&gt;</span><br>
          <br>
          Regards, </div>
        <div>Shwetha<br>
          <br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jun 22, 2020 at 5:01
          PM Felix Kölzow &lt;<a href="mailto:felix.koelzow@gmx.de"
            moz-do-not-send="true">felix.koelzow@gmx.de</a>&gt; 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>
            <p>Dear Shwetha,</p>
            <p><br>
            </p>
            <p>sorry, one more question, since I try to collect some
              more information which may helpful for other
              gluster-users.</p>
            <p>Does the suggested command <br>
            </p>
            <p># setfattr -n glusterfs.geo-rep.trigger-sync -v "1"
              &lt;file-path&gt;</p>
            <p>also work regardless of the current mode, i.e. history,
              hybrid or changelog crawl?</p>
            <p><br>
            </p>
            <p>Regards,</p>
            <p>Felix<br>
            </p>
            <div>On 22/06/2020 13:11, Shwetha Acharya wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">Hi Felix,<br>
                <br>
                <div>File path is the path from mount point. Need not
                  include any other options.<br>
                  <br>
                  Regards,|<br>
                  Shwetha</div>
              </div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Mon, Jun 22, 2020
                  at 3:15 PM Felix Kölzow &lt;<a
                    href="mailto:felix.koelzow@gmx.de" target="_blank"
                    moz-do-not-send="true">felix.koelzow@gmx.de</a>&gt;
                  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">Dear Shwetha,<br>
                  <br>
                  &gt; One more alternative would be to triggering sync
                  on indivisual files,<br>
                  &gt; # setfattr -n glusterfs.geo-rep.trigger-sync -v
                  "1" &lt;file-path&gt;<br>
                  <br>
                  So, how to do it exactly and what is
                  &lt;file-path&gt;? Is it a gluster mount<br>
                  point with certain mount options<br>
                  <br>
                  or is this the brick path? Furthermore, does it work
                  for directories?<br>
                  <br>
                  <br>
                  Regards,<br>
                  <br>
                  Felix<br>
                  <br>
                  <br>
                  ________<br>
                  <br>
                  <br>
                  <br>
                  Community Meeting Calendar:<br>
                  <br>
                  Schedule -<br>
                  Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
                  Bridge: <a href="https://bluejeans.com/441850968"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://bluejeans.com/441850968</a><br>
                  <br>
                  Gluster-users mailing list<br>
                  <a href="mailto:Gluster-users@gluster.org"
                    target="_blank" moz-do-not-send="true">Gluster-users@gluster.org</a><br>
                  <a
                    href="https://lists.gluster.org/mailman/listinfo/gluster-users"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: <a class="moz-txt-link-freetext" href="https://bluejeans.com/441850968">https://bluejeans.com/441850968</a>

Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a>
</pre>
    </blockquote>
  </body>
</html>