I wonder what happens in the case of two racing "crm" commands that want to update the CIB (with non-overlapping/conflicting data). Is there any locking to ensure that one crm cannot overwrite the other's change? (i.e. second one to get there has to read in the new CIB before being able to apply his change and send it back) Or if there is a situation where one write stomps another's, is there at least some kind of notification?
Ultimately, it would be bad for two nodes for example to issue: # crm node attribute $(uname -n) set name value at the same time and have one of those updates lost. But that's what I think I am seeing. Cheers, b.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
