From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] CMAN/DLM without SCTP
Date: Wed, 19 Feb 2014 12:13:42 -0600 [thread overview]
Message-ID: <20140219181342.GC21855@redhat.com> (raw)
In-Reply-To: <CAH0fbtNiu3BaWdrNpEuKOMNMAquW3B6qgfQ6ZPTGXQujaTXXQw@mail.gmail.com>
On Tue, Feb 18, 2014 at 07:03:44PM +0530, Pratik Mehta wrote:
> Hi,
> I am trying to use a cluster with Pacemaker + CMAN on CentOS 6.4. The
> application that runs on the cluster includes a userspace SCTP stack.
> However CMAN loads dlm which loads the Linux kernel sctp module, which
> interferes with the userspace SCTP.
>
> I do not have any GFS/locking requirements on this cluster. I use a 2 node
> cluster to failover a bunch of IP addresses.
>
> I tried setting DLM_CONTROLD_OPTS="-r 0" and blacklisting sctp module.
> Didn't help since dlm depends on sctp and cman loads dlm.
>
> In /etc/init.d/cman:
> errmsg=$( modprobe dlm 2>&1 ) || return 1
> errmsg=$( modprobe lock_dlm 2>&1 ) || true
>
> As a hack: I modified the cman service to not load dlm and lock_dlm. The
> cluster seems working. However I do not know what additional functionality
> was broken when I disabled these. Though a hack: I am eager to know if
> someone sees an issue of running a production cluster with this.
That's a fine solution. You might also be able to use
'service cman start quorum'. The cman init script could probably
use some sysconfig option to either disable dlm/gfs2/etc or to
tell it to quit after the quorum step.
> Another options is to introduce a compile time flag in the DLM kernel
> module to not use SCTP.
Not long ago it was possible to avoid loading sctp, but people kept adding
sctp symbols and I didn't have to time to try to keep them out. It would
be nice if that could be corrected again.
Dave
next prev parent reply other threads:[~2014-02-19 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 13:33 [Cluster-devel] CMAN/DLM without SCTP Pratik Mehta
2014-02-19 18:13 ` David Teigland [this message]
2014-02-26 11:22 ` Pratik Mehta
2014-02-26 16:10 ` 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=20140219181342.GC21855@redhat.com \
--to=teigland@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).