Re: Production cluster planning

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



That's not correct. There is no risk of corruption using "sync=disabled". In the worst case you just end up with old data but no corruption. See the following comment from a master of ZFS (Aaron Toponce):

https://pthree.org/2013/01/25/glusterfs-linked-list-topology/#comment-227906

Btw: I have enterprise SSD for my ZFS SLOG but in the case of GlusterFS I see not much improvement. The real performance improvement comes by disabling ZFS synchronous writes. I do that for all my ZFS pools/partitions which have GlutserFS on top.






-------- Original Message --------
Subject: Re: [Gluster-users] Production cluster planning
Local Time: September 26, 2016 11:08 PM
UTC Time: September 26, 2016 9:08 PM
From: lindsay.mathieson@xxxxxxxxx
To: gluster-users@xxxxxxxxxxx

On 27/09/2016 4:13 AM, mabi wrote:
> I would also say do not forget to set "sync=disabled".

I wouldn't be doing that - very high risk of gluster corruption in the
event of power loss or server crash. Up to 5 seconds of writes could be
lost that way.


If writes aren't fast enough I'd add a SSD partition for slog.
Preferably a data center quality one.

--
Lindsay Mathieson

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux