From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman-kernel/src membership.c
Date: 26 Jun 2006 08:54:38 -0000 [thread overview]
Message-ID: <20060626085438.30850.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: STABLE
Changes by: pcaulfield at sourceware.org 2006-06-26 08:54:37
Modified files:
cman-kernel/src: membership.c
Log message:
If we get a Master-HELLO and we are not the master for this transition then
kick off a new one to resolve the ambiguity.
I reckon this was probably the cause of the first trouble in bz#194491
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman-kernel/src/membership.c.diff?cvsroot=cluster&only_with_tag=STABLE&r1=1.44.2.18.6.6&r2=1.44.2.18.6.7
--- cluster/cman-kernel/src/Attic/membership.c 2006/05/09 10:37:08 1.44.2.18.6.6
+++ cluster/cman-kernel/src/Attic/membership.c 2006/06/26 08:54:36 1.44.2.18.6.7
@@ -2882,6 +2882,13 @@
}
}
+ /* If we get a master hello and we are not the master then start a CHECK transition, cos the
+ real master must have gone away in a period of confusion */
+ if (node_state != MASTER && hellomsg->flags & HELLO_FLAG_MASTER) {
+ node = find_node_by_nodeid(saddr->scl_nodeid);
+ start_transition(TRANS_CHECK, node);
+ }
+
return 0;
}
next reply other threads:[~2006-06-26 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 8:54 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-19 15:01 [Cluster-devel] cluster/cman-kernel/src membership.c pcaulfield
2007-05-03 10:19 pcaulfield
2007-01-19 16:21 pcaulfield
2007-01-19 16:20 pcaulfield
2007-01-18 15:10 pcaulfield
2007-01-18 15:08 pcaulfield
2006-06-26 14:13 pcaulfield
2006-06-26 8:42 pcaulfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060626085438.30850.qmail@sourceware.org \
--to=pcaulfield@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.