[Pacemaker] Fwd: [Openais] cpg behavior on transitional membership change

[Jiaju Zhang]

Seems this mail being truncated while sending, so post it again;)
Also this time I CCed pacemaker mailing list as well.

---------- Forwarded message ----------
From: Jiaju Zhang <jjzhang.linux at gmail.com>
Date: Sun, Sep 4, 2011 at 12:52 AM
Subject: Re: [Openais] cpg behavior on transitional membership change
To: Vladislav Bogdanov <bubble at hoster-ok.com>
Cc: David Teigland <teigland at redhat.com>,
"Openais at lists.linux-foundation.org"
<Openais at lists.linux-foundation.org>


On Fri, Sep 02, 2011 at 10:12:11PM +0300, Vladislav Bogdanov wrote:
> 02.09.2011 20:55, David Teigland wrote:
> [snip]
> >
> > I really can't make any sense of the report, sorry.  Maybe reproduce it
> > without pacemaker, and then describe the specific steps to create the
> > issue and resulting symptoms.  After that we can determine what logs, if
> > any, would be useful.
> >
>
> I just tried to ask a question about cluster components logic based on
> information I discovered from both logs and code analysis. I'm sorry if
> I was unclear in that, probably some language barrier still exists.
>
> Please see my previous mail, I tried to add some explanations why I
> think current logic is not complete.

Hi Vladislav, I guess I have known the problem what you described;)
I'd like to give a example to make the things more clear.

3-node cluster, for whatever reason, especially on heavy workload,
corosync may detect one node disappear and reappear again. So the
membership information changes are as follows:
membership 1: nodeA, nodeB, nodeC
membership 2: nodeB, nodeC
membership 3: nodeA, nodeB, nodeC