<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 02/25/2016 06:01 PM, ABHISHEK
      PALIWAL wrote:<br>
    </div>
    <blockquote
cite="mid:CA+15cFOqmsi0pM4ctv0+KD-o7M+j42Z8Qx2u3Qj5rKYursCO_A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>Hi,<br>
                <br>
              </div>
              Here, I have one query regarding the time taken by the
              healing process.<br>
            </div>
            In current two node setup when we rebooted one node then the
            self-healing process starts less than 5min interval on the
            board which resulting the corruption of the some files data.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Heal should start immediately after the brick process comes up. What
    version of gluster are you using? What do you mean by corruption of
    data? Also, how did you observe that the heal started after 5
    minutes?<br>
    -Ravi<br>
    <blockquote
cite="mid:CA+15cFOqmsi0pM4ctv0+KD-o7M+j42Z8Qx2u3Qj5rKYursCO_A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          And to resolve it I have search on google and found the
          following link:<br>
          <a moz-do-not-send="true"
            href="https://support.rackspace.com/how-to/glusterfs-troubleshooting/"
            target="_blank">https://support.rackspace.com/how-to/glusterfs-troubleshooting/</a><br>
          <br>
        </div>
        <div>Mentioning that the healing process can takes upto 10min of
          time to start this process.<br>
          <br>
        </div>
        <div>Here is the statement from the link:<br>
          <br>
          "Healing replicated volumes
          <br>
          <br>
          When any brick in a replicated volume goes offline, the
          glusterd daemons on the remaining nodes keep track of all the
          files that are not replicated to the offline brick. When the
          offline brick becomes available again, the cluster initiates a
          healing process, replicating the updated files to that brick.
          <b>The start of this process can take up to 10 minutes, based
            on observation.</b>"
          <br>
        </div>
        <div><br>
        </div>
        <div>After giving the time of more than 5 min file corruption
          problem has been resolved.<br>
        </div>
        <div><br>
        </div>
        <div>So, Here my question is there any way through which we can
          reduce the time taken by the healing process to start?<br>
          <br>
        </div>
        <br>
        Regards,<br>
        Abhishek Paliwal<br clear="all">
        <br>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Gluster-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a></pre>
    </blockquote>
    <br>
    <br>
  </body>
</html>