All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christine Caulfield <ccaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] disallowed in cluster3
Date: Thu, 06 Aug 2009 08:08:37 +0100	[thread overview]
Message-ID: <4A7A8175.3010109@redhat.com> (raw)
In-Reply-To: <20090805165234.GB17292@redhat.com>

On 05/08/09 17:52, David Teigland wrote:
> When rewriting daemons for cluster3 to remove groupd, I wrote them to not need
> or use the disallowed-nodes feature from cman for handling remerging of
> cluster partitions.  In compat mode, however, (the cluster2 code) they would
> still depend on that cman feature, which is why it still exists in cluster3
> cman.
>
> I've found, though, that when we do have a partition remerge, cman's
> disallowed feature gets in the way of the daemons trying to handle it
> themselves (which I'm testing, it doesn't seem quite right in all
> partitioning/merging cases yet.)
>
> So, I think what we need is for cluster3 cman to turn off the disallowed
> feature unless the cluster is in compat mode, i.e.<group groupd_compat="1"/>
> exists.


Thanks, I've been looking for an excuse to add code to cluster3 to 
disable that mode ;-)

I'm not happy with cman reading groupd tags out of cluster.conf though. 
The alternatives are to have an extra tag for cman, but that risks users 
only setting one or the other and causing havoc. So how about a higher 
level <cluster compat="x"> flag ?

Chrissie



  reply	other threads:[~2009-08-06  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 16:52 [Cluster-devel] disallowed in cluster3 David Teigland
2009-08-06  7:08 ` Christine Caulfield [this message]
2009-08-06 14:04   ` David Teigland
2009-08-06 17:39   ` Fabio M. Di Nitto
2009-08-12 21:48   ` David 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=4A7A8175.3010109@redhat.com \
    --to=ccaulfie@redhat.com \
    /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.