<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font color="#000099">Thank you very much!</font><br>
<br>
<div class="moz-cite-prefix">On Monday 28 April 2014 07:41 AM,
Ravishankar N wrote:<br>
</div>
<blockquote cite="mid:535DB8EB.2060202@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 04/28/2014 01:30 AM, Chalcogen
wrote:<br>
</div>
<blockquote cite="mid:535D61D3.7040509@yahoo.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font color="#000099">Hi everyone,<br>
<br>
I have trouble understanding the following behavior:<br>
<br>
Suppose I have a replica 2 volume 'testvol' on two servers,
server1 and server2, composed of server1:/bricks/testvol/brick
and server2:/bricks/testvol/brick. Also, suppose it contains a
good number of files.<br>
<br>
Now, assume I remove one of the two bricks, as:</font><br>
<br>
root@server1~# gluster volume remove-brick testvol replica 1
server1:/bricks/testvol/brick<br>
<font color="#000099"><br>
Now, I unmount and delete the logical volume supporting the
brick and then recreate it (with a different size), and mount
it the same way as it was mounted before (at /brick/testvol/).
Then, I re-add it as:</font><br>
<br>
root@server1~# gluster volume add-brick testvol replica 2
server1:/bricks/testvol/brick<br>
<font color="#000099"><br>
I observe that the brick on server1 does not contain any of
the data that was in the volume.</font><br>
<br>
root@server1~# ls /bricks/testvol/brick<br>
root@server1~# <br>
<br>
<font color="#000099">This is all right by me, since glusterfs
needs some time to discover and sync files that are absent on
the brick of server1. In fact, if I leave the setup
undisturbed for 15 minutes to half an hour, I find that all
data appears within the brick of server1, just as you would
expect. Also, if I wish to speed up the process, I simply do a
ls -Ra on the directory where the volume is mounted, and all
files sync onto server1's brick. This is also very much as
expected.<br>
<br>
However, during the period where data on server1's brick is
not available, if you query the heal info for the volume,
gluster cli reports that 'Number of entries' is '0', and that
too all of 'info', 'heal-failed', and 'split-brain'. This is
what becomes a bit of a trouble for me. Fact is, we are
attempting to automate the monitoring of our glusterfs
volumes, and we depend upon heal info alone to decide whether
data on server1 and server2 are in sync. <br>
<br>
Could somebody, therefore, help me with the following
questions?<br>
a) Which files exactly show up in heal info?<br>
</font></blockquote>
<font color="#000099">The files which are healed either by the
self-heal daemon or</font> by the gluster heal commands.<br>
<blockquote cite="mid:535D61D3.7040509@yahoo.com" type="cite"><font
color="#000099"> b) What exactly should I look to monitor if
we are to ascertain that data on our servers are in sync?<br>
<br>
</font></blockquote>
<font color="#000099">After adding a new replica brick, you need
to run a full heal (gluster volume heal <vol-name> full).
Then the </font>results will show up in the heal info output.<br>
<blockquote cite="mid:535D61D3.7040509@yahoo.com" type="cite"><font
color="#000099"> Thanks a lot for your responses!</font><br>
<font color="#000099"><br>
Anirban<br>
<br>
P.s. I am using glusterfs 3.4.2 over linux kernel version
2.6.34.<br>
</font><br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>