On Thu, Jun 07, 2012 at 08:34:56AM -0400, Pranith Kumar Karampuri wrote: > Brian, > Small correction: 'sending queries to *both* servers to check they are in sync - even read accesses.' Read fops like stat/getxattr etc are sent to only one brick. Is that new behaviour for 3.3? My understanding was that stat() was a healing operation. http://gluster.org/community/documentation/index.php/Gluster_3.2:_Triggering_Self-Heal_on_Replicate If this is no longer true, then I'd like to understand what happens after a node has been down and comes up again. I understand there's a self-healing daemon in 3.3, but what if you try to access a file which has not yet been healed? I'm interested in understanding this, especially the split-brain scenarios (better to understand them *before* you're stuck in a problem :-) BTW I'm in the process of building a 2-node 3.3 test cluster right now. Cheers, Brian.
