> Since every node sees every message in the same order there is never a > need for locks. An example of why not is creation of a resource called > "datasetA". > > 3 nodes: > node A sends "create datasetA" > node B sends "create datasetA" > node C sends "create datasetA" > > Only one of those nodes create dataset will arrive first. The > remainder > will arrive second and third. Also, vs requires that each node sends > in > the same order so it may be something like on all nodes: > B received, C received, A received. > > In this case, B creates the dataset, C says "dataset exists" A says > "dataset exists". All nodes see this same ordering
OK, thank for that verbose example. I guess I understand that so far - it is basically a distributed state machine. But I want to get the 'result' of command, for example: > node B sends "create datasetA" > node B want to know if that was successful cpg_mcast_joined sends messages asynchrounous. Is there a way to wait until the message is delivered to the local callback? Or do I need to implement my own message numbering scheme to detect when a message arrives? And, if I send a message with 'cpg_mcast_joined', is there any guarantee that this message arrives at the local node callback? In other words, can I trust that I receive messages sent by myself? If so, is there a timing constraint (something like, messages sent will arrive within 10 second at the local node)? - Dietmar _______________________________________________ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais
