cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Beekhof <andrew@beekhof.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm_controld.pcmk: Fix membership change judging issue
Date: Fri, 14 May 2010 12:15:12 +0200	[thread overview]
Message-ID: <AANLkTileA1uu1r8X_3znI9W5pR5Ner-jsD9V-tUqz17S@mail.gmail.com> (raw)
In-Reply-To: <4BED4A430200000A00011FE2@novprvlin0050.provo.novell.com>

On Fri, May 14, 2010 at 5:04 AM, Tim Serong <tserong@novell.com> wrote:
> On 5/14/2010 at 06:19 AM, Andrew Beekhof <andrew@beekhof.net> wrote:
>>
>> Does the behavior still occur with pacemaker 1.1.2?
>>
>
> Yes.
>
> For the record, the most minimal testcase I've managed for this
> so far is as follows (substitute "/etc/init.d/corosync start" or
> whatever for "rcopenais start" if you're not on something SUSE-based):
>
> 1) Configure corosync/openais on two nodes.
> ? Do not start the cluster yet.
>
> 2) On one node:
>
> ? ? # rm /var/lib/heartbeat/crm/*
> ? ? # rcopenais start
> ? ? # while ! crm_mon -1 | grep -qi online; do \
> ? ? ? ? echo -n "." ; sleep 5 ; done
>
> 3) Now we have one node online, configure Pacemaker:
>
> ? ? # cat <<CONF | crm configure
> ? ? primitive dlm ocf:pacemaker:controld
> ? ? primitive clvm ocf:lvm2:clvmd
> ? ? group g dlm clvm
> ? ? clone c g meta interleave="true"
> ? ? property stonith-enabled="false"
> ? ? property no-quorum-policy="ignore"
> ? ? commit
> ? ? CONF
>
> ? Watch "crm_mon -r" until that clone comes online.
> ? Should only take a few seconds.
>
> 4) On the other node:
>
> ? ? # rm /var/lib/heartbeat/crm/*
> ? ? # rcopenais start
>
> The first node will now either wedge up spectacularly, and/or
> dlm_recoverd and clvmd will be stuck in D state on both nodes.

Presumably each thinks the other node isn't a member?
Perhaps something like this will help:

diff -r b59c27dc114a lib/ais/plugin.c
--- a/lib/ais/plugin.c	Wed May 12 10:51:56 2010 +0200
+++ b/lib/ais/plugin.c	Fri May 14 12:12:33 2010 +0200
@@ -498,9 +498,8 @@ static void *pcmk_wait_dispatch (void *a
 		    ais_notice("Respawning failed child process: %s",
 			       pcmk_children[lpc].name);
 		    spawn_child(&(pcmk_children[lpc]));
-		} else {
-		    send_cluster_id();
 		}
+		send_cluster_id();
 	    }
 	}
 	sched_yield ();
@@ -661,6 +660,7 @@ int pcmk_startup(struct corosync_api_v1
 	    }
 	}
     }
+    send_cluster_id();

     return 0;
 }



  reply	other threads:[~2010-05-14 10:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  8:49 [Cluster-devel] [PATCH] dlm_controld.pcmk: Fix membership change judging issue Jiaju Zhang
     [not found] ` <20100513095117.GM20952@suse.de>
2010-05-13 10:18   ` Jiaju Zhang
2010-05-13 16:25   ` Andrew Beekhof
     [not found]     ` <20100513183215.GP20952@suse.de>
2010-05-13 20:19       ` Andrew Beekhof
2010-05-14  3:04         ` Tim Serong
2010-05-14 10:15           ` Andrew Beekhof [this message]
2010-05-14 11:28             ` Jiaju Zhang
     [not found]         ` <20100513203604.GQ20952@suse.de>
2010-05-14  9:52           ` Andrew Beekhof
2010-05-14 11:25             ` Jiaju Zhang
2010-05-14  4:08     ` Jiaju Zhang
2010-05-14  5:33       ` Jiaju Zhang

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=AANLkTileA1uu1r8X_3znI9W5pR5Ner-jsD9V-tUqz17S@mail.gmail.com \
    --to=andrew@beekhof.net \
    /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).