From: Ryan McCabe <rmccabe@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] when do I need to start cpglockd
Date: Thu, 14 Jun 2012 08:21:24 -0400 [thread overview]
Message-ID: <20120614122123.GA823262@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F754B94A0A9@lisa.maurer-it.com>
On Wed, Jun 13, 2012 at 03:26:22PM +0000, Dietmar Maurer wrote:
> I just tried to upgrade my packages form STABEL31 to STABLE32, and noticed that there is a new daemon 'cpglockd'
>
> That daemon is always started with the default init script. Is that really necessary?
>
> I just wonder why rgmanager needs 2 different locking mechanism - dlm and cpglockd?
[snip]
> But why do I want to enable CPG-based locking, or why not?
Cpglockd was created to work around problems (mainly very slow failover) when
corosync's RRP mode is enabled and dlm locking is used. It will be
started from the cman init script only when RRP mode is detected. In
this case, dlm locks won't be used at all by rgmanager.
Ryan
next prev parent reply other threads:[~2012-06-14 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 15:26 [Cluster-devel] when do I need to start cpglockd Dietmar Maurer
2012-06-14 12:21 ` Ryan McCabe [this message]
2012-06-14 15:41 ` Dietmar Maurer
2012-06-14 16:06 ` Ryan McCabe
2012-06-19 3:44 ` Fabio M. Di Nitto
2012-06-19 4:23 ` Dietmar Maurer
2012-06-19 6:20 ` Fabio M. Di Nitto
2012-06-19 6:54 ` Dietmar Maurer
2012-06-19 7:03 ` Fabio M. Di Nitto
2012-06-19 7:24 ` Dietmar Maurer
2012-06-19 8:04 ` Fabio M. Di Nitto
2012-06-19 8:12 ` Dietmar Maurer
2012-06-19 8:33 ` Fabio M. Di Nitto
2012-06-19 8:36 ` Dietmar Maurer
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=20120614122123.GA823262@redhat.com \
--to=rmccabe@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).