<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 05/27/2015 08:48 PM, Pedro Oriani
wrote:<br>
</div>
<blockquote cite="mid:SNT146-W71009E41D00B73F9D90120A0CB0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Hi All,
<div>I'm writing because I'm experiecing an issue with gluster's
replication feature.</div>
<div>I've a brick on srv1 with about 2TB of mixed side files,
ranging from 10k a 300k</div>
<div>When I add a new replication brick on srv2, the glusterfs
process take all the cpu.</div>
<div>This is unsuitable because the volume is not responding at
normal r/w queries.</div>
<div><br>
</div>
<div>Glusterfs version is 3.7.0</div>
</div>
</blockquote>
Is it because of self-heals? Was the brick offline until then?<br>
<br>
Pranith<br>
<blockquote cite="mid:SNT146-W71009E41D00B73F9D90120A0CB0@phx.gbl"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>the underlaying volume is xfs.</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>Volume Name: vol1</div>
<div>Type: Replicate</div>
<div>Volume ID: </div>
<div>Status: Started</div>
<div>Number of Bricks: 1 x 2 = 2</div>
<div>Transport-type: tcp</div>
<div>Bricks:</div>
<div>Brick1: 172.16.0.1:/data/glusterfs/vol1/brick1/brick</div>
<div>Brick2: 172.16.0.2:/data/glusterfs/vol1/brick1/brick</div>
<div>Options Reconfigured:</div>
<div>performance.cache-size: 1gb</div>
<div>cluster.self-heal-daemon: off</div>
<div>cluster.data-self-heal-algorithm: full</div>
<div>cluster.metadata-self-heal: off</div>
<div>performance.cache-max-file-size: 2MB</div>
<div>performance.cache-refresh-timeout: 1</div>
<div>performance.stat-prefetch: off</div>
<div>performance.read-ahead: on</div>
<div>performance.quick-read: off</div>
<div>performance.write-behind-window-size: 4MB</div>
<div>performance.flush-behind: on</div>
<div>performance.write-behind: on</div>
<div>performance.io-thread-count: 32</div>
<div>performance.io-cache: on</div>
<div>network.ping-timeout: 2</div>
<div>nfs.addr-namelookup: off</div>
<div>performance.strict-write-ordering: on</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>there is any parameter or hint that I can follow to limit
cpu occupation to grant a replication with few lag on normal
operations ?</div>
<div><br>
</div>
<div>thank </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>