<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>Thank you very much for this informations. I'm going to test this features right now in my test lab. If it OK, then i implement in my production environnement.</p>
<p> </p>
<div> </div>
<p>Le 21/01/2016 01:42, Krutika Dhananjay a écrit :</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000;">
<div>Right. I'd also like to just add that in its current form, sharding does not support zerofill and discard operations and their development is underway.</div>
<div>As far as fallocate is concerned, it should be possible to use the operation on a sharded volume if it is invoked through posix_fallocate() API.</div>
<div> </div>
<div>Also, in our testing we have found 512MB shard size to provide good performance as far as both IO and self-heal are concerned. I hope that works for you too!</div>
<div> </div>
<div>-Krutika</div>
<div> </div>
<hr id="zwchr" />
<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;"><strong>From: </strong>"Lindsay Mathieson" <lindsay.mathieson@gmail.com><br /><strong>To: </strong>"Krutika Dhananjay" <kdhananj@redhat.com>, "Bello Florent" <florent.bello@ville-kourou.fr><br /><strong>Cc: </strong>gluster-users@gluster.org<br /><strong>Sent: </strong>Thursday, January 21, 2016 6:22:09 AM<br /><strong>Subject: </strong>Re: [Gluster-users] Shard in production<br />
<div> </div>
<div class="moz-cite-prefix">Heh, thanks Krutika.<br /><br /><br /> I believe its pretty much there, have been stress testing it on our production VM cluster for weeks, though not with critical VM's. It is a huge improvement when for the heal process when dealing with large VM's. Failure modes have been very reliable to.<br /><br /> Nb. All my testing has been VM's - e.g a few large files with only one process accessing them. I can't speak to the many thousands of dirs/files use case.<br /><br /><br /> If you are using it for VM hosting (as you are) then it is essential that you set the "virt" group properties, other wise you will end up with VM corruption. These are the settings I've evolved over my testing:<br /><br /><tt><br /></tt><br />
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><tt>Options Reconfigured:</tt><br /><tt>performance.readdir-ahead: off</tt><br /><tt>features.shard: on</tt><br /><tt>features.shard-block-size: 512MB</tt><br /><tt>cluster.self-heal-window-size: 256</tt><br /><tt>server.event-threads: 4</tt><br /><tt>client.event-threads: 4</tt><br /><tt>cluster.quorum-type: auto</tt><br /><tt>cluster.server-quorum-type: server</tt><br /><tt>performance.low-prio-threads: 32</tt><br /><tt>performance.io-thread-count: 32</tt><br /><tt>performance.cache-refresh-timeout: 4</tt><br /><tt>nfs.disable: on</tt><br /><tt>nfs.addr-namelookup: off</tt><br /><tt>nfs.enable-ino32: off</tt><br /><tt>performance.write-behind: off</tt><br /><tt>performance.strict-write-ordering: on</tt><br /><tt>performance.stat-prefetch: off</tt><br /><tt>performance.quick-read: off</tt><br /><tt>performance.read-ahead: off</tt><br /><tt>performance.io-cache: off</tt><br /><tt>cluster.eager-lock: enable</tt><br /><tt>network.remote-dio: enable</tt><br /><tt>cluster.data-self-heal-algorithm: full</tt></blockquote>
<br /><br /><br /> On 21/01/16 02:06, Krutika Dhananjay wrote:</div>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">
<div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000;">
<div>Adding Lindsay Mathieson, who has tested sharding with VM store extensively. :)</div>
<div> </div>
<div>-Krutika</div>
<hr id="zwchr" />
<blockquote style="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;"><strong>From: </strong>"Bello Florent" <a class="moz-txt-link-rfc2396E" href="mailto:florent.bello@ville-kourou.fr"><florent.bello@ville-kourou.fr></a><br /><strong>To: </strong><a class="moz-txt-link-abbreviated" href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br /><strong>Sent: </strong>Wednesday, January 20, 2016 8:12:27 PM<br /><strong>Subject: </strong>[Gluster-users] Shard in production<br />
<div> </div>
<p>Hi,</p>
<p><br /> i see recently the Shard feature is reached to stable. Soon, i want to install oVirt with Gluster Replica Storage and i guess shard feature is good for me. Can i use this feature for my VM Storage production or you guess it's not mature ?</p>
<br /> _______________________________________________<br /> Gluster-users mailing list<br /><a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br /><a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></blockquote>
<div> </div>
</div>
</blockquote>
<br /><br />
<pre class="moz-signature">--
Lindsay Mathieson</pre>
</blockquote>
<div> </div>
</div>
</blockquote>
</body></html>