[Gluster-users] Production cluster planning

mabi mabi at protonmail.ch
Fri Sep 30 18:15:16 UTC 2016

The data will not be in "any" state as you mention or please define what you mean by "any". In the worst case you will just loose 5 seconds of data that's all as far as I understand.

Here is another very interesting but long post regarding this topic. Basically it all boils down to this specific

-------- Original Message --------
Subject: Re: [Gluster-users] Production cluster planning
Local Time: September 30, 2016 12:41 PM
UTC Time: September 30, 2016 10:41 AM
From: lindsay.mathieson at gmail.com
To: mabi <mabi at protonmail.ch>, Gluster Users <gluster-users at gluster.org>

On 29/09/2016 4:32 AM, mabi wrote:
> hat'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

Your missing what he said - *ZFS* will not be corrupted but the data
written could be in any state, in this case the gluster filesystem data
and meta data. To have one ndoe in a cluster out of sync with out the
cluster knowing would be very bad.

Lindsay Mathieson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160930/102a1ae5/attachment.html>

More information about the Gluster-users mailing list