[Openais] corosync - CPG model_init + callback with totem ringid and members

Jan Friesse jfriesse at redhat.com
Fri Apr 9 00:33:30 PDT 2010


Dave,

> 
> Oh, and I may have just invented a time machine by merging partitioned
> clusters!
> 
> 1270661597 cluster node 1 added seq 2128
> 1270661597 fenced:daemon conf 3 1 0 memb 1 2 4 join 1 left
> 1270661597 cpg_mcast_joined retried 4 protocol
> 1270661597 fenced:daemon ring 1:2128 3 memb 1 2 4
> 1270661597 fenced:default conf 3 1 0 memb 1 2 4 join 1 left  (*)
> 1270661597 add_change cg 5 joined nodeid 1
> 1270661597 add_change cg 5 counts member 3 joined 1 remove 0 failed 0
> 1270661597 check_ringid cluster 2128 cpg 2:2124
> 1270661597 fenced:default ring 1:2128 3 memb 1 2 4  (**)
> 1270661597 check_ringid done cluster 2128 cpg 1:2128
> 1270661597 check_quorum done
> 
> * confchg callback adding node 1
> ** totem callback adding node 1

this is something little different and it is one of your requirements.

Two nodes as example is enough:

- Starting corosync on node1
- Starting cpg app (app1) on node1
- app1 receive confchg callback and if desired totem callback
- Starting corosync on node2
- app1 receive totem callback

^^^^ this is what Chrissie is talking about. totem callback precede 
confch callback

- starting cpg app (app2) on node2
   - app2 receive confchg callback and if desired totem callback
   - app1 receive confchg
SPLIT
   - app1 receive confchg callback and totem callback
   - app2 receive confchg callback and totem callback
MERGE
   - app1 receive confchg callback and totem callback
   - app2 receive confchg callback and totem callback

^^^ This is what you are talking about. Confchg precede totem callback 
(as your requirements)

Simply because app1/2 are in time of merge running.

Anyway, can you please send me (exactly) what problem (original problem) 
are you trying to solve?

Regards,
   Honza



More information about the Openais mailing list