From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan McCabe Date: Thu, 14 Jun 2012 08:21:24 -0400 Subject: [Cluster-devel] when do I need to start cpglockd In-Reply-To: <24E144B8C0207547AD09C467A8259F754B94A0A9@lisa.maurer-it.com> References: <24E144B8C0207547AD09C467A8259F754B94A0A9@lisa.maurer-it.com> Message-ID: <20120614122123.GA823262@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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