> I think your example is very vague, what kind of driver you use? Sheep itself
> won't sense membership and rely on cluster drivers to maintain
> membership. Could you detail how it happen exactly in real case?

Membership change can happen for many reason. It  can happen if something is
wrong on the switch (or if some admin configures the switch), a damaged network 
cable, 
a bug in the bonding driver, a damaged network card, or simply a power failure 
on a node, 
which reconnects after power is on....

In Literature, the problem is also known as 'Babbling idiot' (Realtime people 
use that term). A single node
can make the whole system unusable.

- Dietmar 

-- 
sheepdog mailing list
[email protected]
http://lists.wpkg.org/mailman/listinfo/sheepdog

Reply via email to