On Thu, 2009-04-09 at 17:17 -0700, Joel Becker wrote: > On Thu, Apr 09, 2009 at 04:09:18PM -0500, David Teigland wrote: > > On Thu, Apr 09, 2009 at 03:50:08PM -0500, David Teigland wrote: > > > On Thu, Apr 09, 2009 at 10:12:43PM +0200, Andrew Beekhof wrote: > > > > On Thu, Apr 9, 2009 at 20:49, Joel Becker <joel.bec...@oracle.com> > > > > wrote: > > > > > On Thu, Apr 09, 2009 at 01:50:18PM +0200, Andrew Beekhof wrote: > > > > >> For added fun, a node that restarts quickly enough (think a VM) won't > > > > >> even appear to have left (or rejoined) the cluster. > > > > >> At the next totem confchg event, It will simply just be there again > > > > >> with no indication that anything happened. > > > > > > > > > > ? ? ? ?This had BETTER not happen. > > > > > > > > It does, I've seen it enough times that Pacemaker has code to deal with > > > > it. > > > > > > I'd call that a serious flaw we need to get fixed. I'll see if I can > > > make it > > > happen here. > > > > That was pretty simple. > > - set token to 5 minutes > > - nodes 1,2,3,4 are cluster members and members of a cpg > > - on node4: ifdown eth0, kill corosync, ifup eth0, start corosync > > - nodes 1,2,3 seem completely unaware that 4 ever went away > > > > When node 4 joins the cpg after coming back, the cpg on nodes 1,2,3 think > > that > > a new fifth process/node is joining the cpg. The cpg on node 4 shows itself > > being added as a new fourth cpg member. > > Steve, > If node 4's old process went away, shouldn't we be getting a > 'leave' for that, rather than it persisting in the member list? > > Joel >
I'd like to clear up that when Andrew talks about the membership not generating a leave event for totem processes in this scenario (which he integrates directly with), this is true. But cpg should generate a leave event. _______________________________________________ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais
