From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [RFC]Drop unused plock resource when no other plock request comes
Date: Mon, 24 Aug 2009 09:31:29 -0500 [thread overview]
Message-ID: <20090824143128.GA25798@redhat.com> (raw)
In-Reply-To: <f8c992a30908230200g38129b0ne2af968e8ead8a72@mail.gmail.com>
On Sun, Aug 23, 2009 at 05:00:44PM +0800, Jiaju Zhang wrote:
> It seems no chance to trigger the drop_resources to work if there is no
> other plock requests (which are requesting for another lock resource) come
> from node A.
> But I still wonder if there is a way to improve this?
You're correct; yes the daemon could easily be changed to drop resources when
there's no locking activity. We'd just set a poll timeout when
plock_resources is non-empty and call drop_resources() if it times out.
(If you simply want to work around this, you can write a little program to
lock a file on the fs to trigger the drop.)
Dave
next prev parent reply other threads:[~2009-08-24 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 9:00 [Cluster-devel] [RFC]Drop unused plock resource when no other plock request comes Jiaju Zhang
2009-08-24 14:31 ` David Teigland [this message]
2009-08-25 3:10 ` [Cluster-devel] " Jiaju Zhang
2009-08-25 15:35 ` David Teigland
2009-08-26 6:54 ` Jiaju Zhang
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=20090824143128.GA25798@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).