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

[Yanfei Wang]

Hi,

https://docs.gluster.org/en/v3/Administrator%20Guide/arbiter-volumes-and-quorum/,
said,

```
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
other.
```

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


Thanks a lot

- Fei