<div dir="ltr"><div>Hi Joe</div><div><br></div>That makes sense, thanks for the explanation. I'm encouraged now to use ZFS with Gluster.<div><br></div><div>Thanks</div><div><br></div><div>n</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 9, 2014 at 8:34 AM, Joe Julian <span dir="ltr"><<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 10/9/2014 6:23 AM, Nathan Fiedler wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
In the Gluster community documentation, the ZFS Use Case [1] recommends disabling the ZIL (intent log). Any thoughts on why that would be the case? Much of the advice on tuning ZFS recommends against disabling the ZIL, so I'm curious if there is a good reason why it should be done with Gluster. The use case document certainly does not provide one.<br>
<br></span>
[1] <a href="http://gluster.org/documentation/use_cases/GlusterOnZFS/" target="_blank">http://gluster.org/<u></u>documentation/use_cases/<u></u>GlusterOnZFS/</a><br>
</blockquote>
<br>
I've not done that myself but from how I read that document, the user did that because he instead configured an ARC cache to use up to 75% of the machine's 24Gb of RAM. This prevents the double-write of using an on disk journal at the cost of losing data in the event of power loss.<br>
______________________________<u></u>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.<u></u>org/mailman/listinfo/gluster-<u></u>users</a><br>
</blockquote></div><br></div>