[Gluster-devel] How gluster handle split-brain in the corner case from non-overlapping range lock in same file?

Yanfei Wang backyes at gmail.com
Sat May 5 16:34:10 UTC 2018



There is a corner case even with replica 3 volumes where the file can
end up in a split-brain. AFR usually takes range locks for the
{offset, length} of the write. If 3 writes happen on the same file at
non-overlapping {offset, length} and each write fails on (only) one
different brick, then we have AFR xattrs of the file blaming each

Could some body give more details on it? Any clues are welcome.

Thanks a lot

- Fei

More information about the Gluster-devel mailing list