On 1/10/2016 4:15 AM, mabi wrote:
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.
By "Any" state I mean *Any*, you have no way of predicting how much data would be written.
The key thing here is that gluster will think the data has been safely written to disk when it has not. Imagine you have a three node volume undergoing heavy writes. Easily time for multiple shards or small files to be written in 5 seconds.
All of a sudden one of the nodes goes down - perhaps the cleaner unplugged it.
Now the third node is missing up to 5 seconds of data compared to the other two nodes - your gluster volume is in a inconsistent state and *doesn't* know it.
-- Lindsay Mathieson _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users