<div dir="ltr"><div class="gmail_quote"><div style="word-wrap:break-word"><div><div>720b3d4a27f938868cca92ab5fd8252859555476 <blockquote type="cite"><div dir="ltr"><p><span lang="EN-US"><br></span></p><p><span lang="EN-US">I have a replication volume as bellows:</span></p>
<div><span lang="EN-US"> </span><br>
</div><p><span lang="EN-US" style="background-color:olive">[root@gluster001
disk]# gluster volume info rep</span></p><div><span lang="EN-US" style="background-color:olive"> </span><br></div><p><span lang="EN-US" style="background-color:olive">Volume
Name: rep</span></p><p><span lang="EN-US" style="background-color:olive">Type:
Replicate</span></p><p><span lang="EN-US" style="background-color:olive">Volume
ID: 0f7eb8a0-92d7-4911-b766-f23ed870cf3d</span></p><p><span lang="EN-US" style="background-color:olive">Status:
Started</span></p><p><span lang="EN-US" style="background-color:olive">Number
of Bricks: 1 x 2 = 2</span></p><p><span lang="EN-US" style="background-color:olive">Transport-type:
tcp</span></p><p><span lang="EN-US" style="background-color:olive">Bricks:</span></p><p><span lang="EN-US" style="background-color:olive">Brick1:
gluster001:/disk/sdc</span></p><p><span lang="EN-US" style="background-color:olive">Brick2:
gluster002:/disk/sdb</span><span lang="EN-US"></span></p><div><span lang="EN-US"> </span><br></div><p><span lang="EN-US">The sdc and sdb are both raid5 device in 3 SAS
disks.</span></p><div><span lang="EN-US"> </span><br></div><p><span lang="EN-US">And I have 3 clients
(gluster-client001,gluster-client002,gluster-client003) mount on the same
replication volume.To test the self-heal function, I clean gluster001:/disk/sdc
(rm –rf /disk/sdc/*), and run “gluster volume heal rep full”. I use the iftop to
check the process and I get the log :</span></p><p><span lang="EN-US"> <img alt="ÄÚǶͼƬ 2" width="150" height="52" src="cid:ii_1407b4e0fb1c912f">The clients are 172.18.4.17, 172.18.4.19
and 172.18.4.20. There are no jobs running on the clients. But from the log,
the client 4.17 and 4.19 are reading something from the gluster002 server. And
the self-heal process’s performance seems to be affected, only 253Mb/s.</span></p><div><span lang="EN-US"> </span><br></div><p><span lang="EN-US">My Questions, thanks:</span></p><p><span lang="EN-US">@1: why/what are the clients 4.17 and 4.19
reading from gluster002? </span></p>
<span lang="EN-US" style="font-size:12pt;font-family:Cambria">@2: how to accelerate the self-heal?</span> <br></div>
<br><br><br><div style="margin:0px"><span style="font-family:Helvetica;font-size:medium;color:rgb(127,127,127)"><b>From: </b></span><span style="font-family:Helvetica;font-size:medium"><a href="mailto:gluster-users-request@gluster.org" target="_blank">gluster-users-request@gluster.org</a><br>
</span></div><div style="margin:0px"><span style="font-family:Helvetica;font-size:medium;color:rgb(127,127,127)"><b>Subject: </b></span><span style="font-family:Helvetica;font-size:medium"><b>confirm 720b3d4a27f938868cca92ab5fd8252859555476</b><br>
</span></div><div style="margin:0px"><span style="font-family:Helvetica;font-size:medium;color:rgb(127,127,127)"><b>Date: </b></span><span style="font-family:Helvetica;font-size:medium">14 August 2013 6:33:05 AM GMT+01:00<br>
</span></div><br><br>If you reply to this message, keeping the Subject: header intact,<br>Mailman will discard the held message. Do this if the message is<br>spam. If you reply to this message and include an Approved: header<br>
with the list password in it, the message will be approved for posting<br>to the list. The Approved: header can also appear in the first line<br>of the body of the reply.<br><br></blockquote></div><br><div>
<span style="font-family:monospace">--</span><span style="font-family:monospace"><br></span><span style="font-family:monospace">Open Source and Standards @ Red Hat</span><span style="font-family:monospace"><br></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"><a href="http://twitter.com/realjustinclift" target="_blank">twitter.com/realjustinclift</a></span>
</div>
<br></div></div></div><br></div>