<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 10/14/2015 09:39 AM, Lindsay
Mathieson wrote:<br>
</div>
<blockquote
cite="mid:CAEMkAmEhwFt5XQh+URP27bfSF-ogvAbp4J=BApjK1wcpqCXFmw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 13 October 2015 at 22:33, Krutika
Dhananjay <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kdhananj@redhat.com" target="_blank">kdhananj@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote style="border-left:2px solid
#1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><span
class="">
<div dir="ltr">
<div>However I managed to create a state where a
file was being healed on all three nodes (probably
y live migrating a VM while it was being healed).
I didn't think that was possible without creating
a split brain problem, but it eventually got all
the way to being healed.<br>
</div>
</div>
</span></blockquote>
<div>I don't think it is possible for heal of this image
to be happening on all three nodes.<br>
</div>
<span class=""></span></blockquote>
</div>
<br>
<br>
</div>
<div class="gmail_extra">I should have recorded the info output,
but it did show the same file being "possibly healed" on all
three nodes.<br>
</div>
</div>
</blockquote>
There seems to be a confusion in understanding how to interpret
output of "gluster volume heal <volname> info". We will
address it by either improving the output or adding some
documentation about how to interpret it.<br>
For now, all it means is that one of the self-heal-daemons or the
mount is doing the heal on that file. The main confusing point seems
to be the fact that the same output is seen on multiple bricks.
Finding intersection/union of the results between bricks will cost
(LOT)more iops, so we went with giving same output multiple
times(when same info is present on more than one brick) as perceived
by each brick. Doesn't mean that each of the bricks is doing the
heal!, afr takes necessary locks to make sure parallel heals don't
happen on the file.<br>
<br>
Pranith<br>
<blockquote
cite="mid:CAEMkAmEhwFt5XQh+URP27bfSF-ogvAbp4J=BApjK1wcpqCXFmw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Gluster 3.6.6<br clear="all">
</div>
<div class="gmail_extra"><br>
-- <br>
<div class="gmail_signature">Lindsay</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>