From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] DLM Shutdown
Date: Wed, 10 Feb 2016 23:08:47 +0100 [thread overview]
Message-ID: <CAHc6FU7=oWgDjbEA+-ivm9Hdb9OAQKwBLkdWYts7uc+iP+4Tpw@mail.gmail.com> (raw)
In-Reply-To: <20160210211630.GA21379@redhat.com>
On Wed, Feb 10, 2016 at 10:16 PM, David Teigland <teigland@redhat.com> wrote:
> OK, yes, but we've wandered into the weeds here. dlm_controld isn't
> involved in lockspace lifetimes, that's the application/libdlm side.
> The question is what behavior the program creating/removing the lockspace
> needs (and if the program is for more than just testing.)
Well, I'm not sure if this is indeed the right question. Sending
dlm_controld a TERM signal is an indication that dlm_controld should
seriously try shutting itself down and should only ignore the request
if it really must. This surely includes removing the default
lockspace, but also lockspaces that don't have active locks; I'm not
so sure about lockspaces with active locks.
It's a design deficiency that dlm_controld doesn't know which
lockspaces are currently in use by any applications; with this
knowledge, it could recycle unused lockspaces after a while.
prev parent reply other threads:[~2016-02-10 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 1:33 [Cluster-devel] DLM Shutdown Andreas Gruenbacher
2016-02-10 17:38 ` David Teigland
2016-02-10 19:48 ` Andreas Gruenbacher
2016-02-10 20:18 ` David Teigland
2016-02-10 20:38 ` Andreas Gruenbacher
2016-02-10 21:16 ` David Teigland
2016-02-10 22:08 ` Andreas Gruenbacher [this message]
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='CAHc6FU7=oWgDjbEA+-ivm9Hdb9OAQKwBLkdWYts7uc+iP+4Tpw@mail.gmail.com' \
--to=agruenba@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.