From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/group/daemon app.c
Date: 12 Oct 2006 14:25:59 -0000 [thread overview]
Message-ID: <20061012142559.19941.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: teigland at sourceware.org 2006-10-12 14:25:59
Modified files:
group/daemon : app.c
Log message:
Handle the case where we're the second node being added to the group
and the only other member fails. We need to go ahead and process
our join.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/daemon/app.c.diff?cvsroot=cluster&r1=1.49&r2=1.50
--- cluster/group/daemon/app.c 2006/10/06 16:55:19 1.49
+++ cluster/group/daemon/app.c 2006/10/12 14:25:58 1.50
@@ -1427,7 +1427,7 @@
{
app_t *a = g->app;
event_t *ev, *rev;
- node_t *node;
+ node_t *node, *us;
struct save_msg *save;
struct nodeid *id, *safe;
int rv = 0;
@@ -1505,6 +1505,31 @@
log_group(g, "rev %d is for group we're waiting to join",
rev->nodeid);
+ /* If the failed node is the only other app member apart
+ from us in the pending membership list, then we must go
+ ahead with our own join event, there will be no remote nodes
+ processing a rev or an ev for this group. We send a recover
+ message so other nodes waiting to join after us will purge
+ their rev on the group. */
+
+ if (a->node_count == 2) {
+ node = find_app_node(a, rev->nodeid);
+ us = find_app_node(a, our_nodeid);
+
+ if (node && us) {
+ log_group(g, "joining group with one other node"
+ " now dead rev %d", rev->nodeid);
+ a->node_count--;
+ list_del(&node->list);
+ free(node);
+ send_recover(g, rev);
+ del_recovery_set(g, rev, 1);
+ list_del(&rev->list);
+ free_event(rev);
+ return 0;
+ }
+ }
+
/* Look for a remote node with stopped of 1, if we find one,
then fall through to the 'else if (event_state_stopping)'
below. A remote node with stopped of 1 means we've received
next reply other threads:[~2006-10-12 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 14:25 teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-16 15:52 [Cluster-devel] cluster/group/daemon app.c teigland
2006-09-15 20:07 teigland
2006-09-14 20:56 teigland
2006-08-31 18:20 teigland
2006-08-22 14:36 teigland
2006-08-14 21:01 teigland
2006-08-02 20:30 teigland
2006-07-19 19:45 teigland
2006-07-17 18:22 teigland
2006-07-17 17:06 rohara
2006-07-14 20:45 teigland
2006-07-16 7:51 ` Fabio Massimo Di Nitto
2006-07-17 17:08 ` Ryan O'Hara
2006-06-22 21:12 teigland
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=20061012142559.19941.qmail@sourceware.org \
--to=teigland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).