From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence daemon problems
Date: Tue, 09 Oct 2012 13:14:39 -0400 [thread overview]
Message-ID: <50745B7F.7030404@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75576A15FF@lisa.maurer-it.com>
On 10/03/2012 12:55 PM, Dietmar Maurer wrote:
>> The intention of that is to prevent an inquorate node/partition from killing a
>> quorate group of nodes that are running normally. e.g. if a 5 node cluster is
>> partitioned into 2/3 or 1/4. You don't want the 2 or 1 node group to fence
>> the 3 or 4 nodes that are fine.
>
> sure, I understand that.
>
>> The difficult cases, which I think you're seeing, are partitions where no group
>> has quorum, e.g. 2/2. In this case we do nothing, and the user has to resolve
>> it by resetting some of the nodes
>
> The problem with that is that those 'difficult' cases are very likely. For example
> a switch reboot results in that state if you do not have redundant network (yes,
> I know that this setup is simply wrong).
>
> And things get worse, because it is not possible to reboot such nodes, because
> rgmanager shutdown simply hangs. Is there any way to avoid that, so that it is at
> least possible to reboot those nodes?
>
Kill rgmanager and/or 'reboot -fn' ?
I thought inquorate reboots worked - please file a bugzilla.
-- Lon
next prev parent reply other threads:[~2012-10-09 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 8:03 [Cluster-devel] fence daemon problems Dietmar Maurer
2012-10-03 9:25 ` Dietmar Maurer
2012-10-03 14:46 ` David Teigland
2012-10-03 16:08 ` Dietmar Maurer
2012-10-03 16:12 ` Dietmar Maurer
2012-10-03 16:24 ` David Teigland
2012-10-03 16:26 ` Dietmar Maurer
2012-10-03 16:44 ` David Teigland
2012-10-03 16:55 ` Dietmar Maurer
2012-10-03 17:10 ` David Teigland
2012-10-09 17:14 ` Lon Hohberger [this message]
2012-10-09 17:13 ` Lon Hohberger
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=50745B7F.7030404@redhat.com \
--to=lhh@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 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).