On 2006-02-02T17:52:48, Andrew Beekhof <[EMAIL PROTECTED]> wrote:
> > That sounds like ultimately an additional barrier might be needed or
> > ultimately a totally ordered messaging service ;-)
> well the CCM membership is supposed to BE the barrier :-)
Well, yes, but apparently it's not delivered on all nodes at the same
time, or rather: not delivered even before some node has reacted to it
(and send a message to the DC), correct?
I wonder if this problem would be "fixed" if the CCM transition leader
was the CRM DC. (Which is probably what is causing this; the CCM
transition leader announces the membership locally, CRM draws faster
than its shadow, while the DC on the other end of the network hasn't yet
heard about the new CCM message.)
Not sure how to best fix this. A delay probably works fine, yet it is
ugly and only covers the issue ;-) If anyone has a better idea...
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
