[Pacemaker] racing crm commands... last write wins?

[Brian J. Murrell]

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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130221/41c5f41b/attachment-0003.sig>