On Mon, Apr 13, 2009 at 02:17:00PM -0500, David Teigland wrote:
On Mon, Apr 13, 2009 at 12:10:33PM -0700, Steven Dake wrote:
On Mon, 2009-04-13 at 13:35 -0500, David Teigland wrote:
0. configure token timeout to some long time that is longer than all the
following steps take
1.
On Wed, May 06, 2009 at 02:10:27PM -0700, Steven Dake wrote:
On Wed, 2009-05-06 at 15:04 -0500, David Teigland wrote:
On Mon, Apr 13, 2009 at 02:17:00PM -0500, David Teigland wrote:
On Mon, Apr 13, 2009 at 12:10:33PM -0700, Steven Dake wrote:
On Mon, 2009-04-13 at 13:35 -0500, David
On Thu, Apr 09, 2009 at 09:58:15PM -0700, Joel Becker wrote:
On Thu, Apr 09, 2009 at 06:06:13PM -0700, Steven Dake wrote:
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),
On Thu, Apr 09, 2009 at 06:02:38PM -0700, Steven Dake wrote:
The issue that Dave is talking about I believe is described in the
following bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=489451
No, not at all.
IMO you should get a leave event for any process that leaves the process
On Mon, 2009-04-13 at 13:35 -0500, David Teigland wrote:
On Thu, Apr 09, 2009 at 06:02:38PM -0700, Steven Dake wrote:
The issue that Dave is talking about I believe is described in the
following bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=489451
No, not at all.
IMO you
On Mon, Apr 13, 2009 at 12:10:33PM -0700, Steven Dake wrote:
On Mon, 2009-04-13 at 13:35 -0500, David Teigland wrote:
0. configure token timeout to some long time that is longer than all the
following steps take
1. cluster members are nodeid's: 1,2,3,4
2. cpg foo has the
On Mon, Apr 13, 2009 at 02:17:00PM -0500, David Teigland wrote:
On Mon, Apr 13, 2009 at 12:10:33PM -0700, Steven Dake wrote:
On Mon, 2009-04-13 at 13:35 -0500, David Teigland wrote:
0. configure token timeout to some long time that is longer than all the
following steps take
1.
Joel Becker wrote:
Steve, Dave, etc,
Someone told me a while back that a node joining a cpg group
would be by its lonesome in the join message. That is, when the node
gets its first confchg, it will be the only node in the list of joins.
I've been using this to detect the first joiner
On Thu, Apr 9, 2009 at 09:37, Chrissie Caulfield ccaul...@redhat.com wrote:
Joel Becker wrote:
Steve, Dave, etc,
Someone told me a while back that a node joining a cpg group
would be by its lonesome in the join message. That is, when the node
gets its first confchg, it will be the only
On 4/9/2009 at 5:50 AM, in message
26ef5e70904090450s40e92dcfgea0fc34826360...@mail.gmail.com, Andrew Beekhof
beek...@gmail.com wrote:
On Thu, Apr 9, 2009 at 09:37, Chrissie Caulfield ccaul...@redhat.com wrote:
Joel Becker wrote:
Steve, Dave, etc,
Someone told me a while back that a
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
On Thu, Apr 09, 2009 at 08:37:00AM +0100, Chrissie Caulfield wrote:
1) If member_count == join count, then it's a safe bet that they are all
new nodes, and yes , it is true that all nodes should see the same
confchg messages
2) if join_count 0 then leave_count will always be zero. That's a
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
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
On Thu, Apr 9, 2009 at 19:15, David Teigland teigl...@redhat.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
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
On Thu, Apr 09, 2009 at 03:17:47PM -0700, Steven Dake wrote:
A proper system using this model doesn't care - it synchronizes every
time regardless of who left or joined based upon whether it has state to
sync that is unique.
Dave,
If we're going to use cpg for our membership, we need
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
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
guarantees you seek, and if it doesn't, it is defective. The only
exception might be if the new process reuses the same PID since the
pid/nodeid/group are the uniqifiers and if pid is the same, there is
no
way to detect the new process (and remove the old one).
PID reuse happens more often
On Thu, Apr 09, 2009 at 06:06:13PM -0700, Steven Dake wrote:
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.
Steve, Dave, etc,
Someone told me a while back that a node joining a cpg group
would be by its lonesome in the join message. That is, when the node
gets its first confchg, it will be the only node in the list of joins.
I've been using this to detect the first joiner of the group (I
22 matches
Mail list logo
