From: David Teigland <teigland@redhat.com>
To: Charles Koprowski <cko@audaxis.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] ubuntu xenial + lvmlockd
Date: Thu, 20 Apr 2017 10:40:48 -0500 [thread overview]
Message-ID: <20170420154048.GA29033@redhat.com> (raw)
In-Reply-To: <CABGge9yUfY02boFs8btDkRpFitwm6ZSAv8YpCRGPOwoV8pLyUQ@mail.gmail.com>
On Thu, Apr 20, 2017 at 11:26:18AM +0200, Charles Koprowski wrote:
> Would you consider the use of lvmlockd + sanlock as "production ready" ?
I believe it will work better than clvmd. There is one main thing, unique
to using sanlock, that you should verify in your environment.
lvmlockd+sanlock is sensitive to spikes in i/o delays. If sanlock sees
several consecutive large i/o delays (> 10 sec each), e.g. during heavy
use from applications, or during path switching, this can trigger spurious
failure detection. (This is analogous to network delays when using
network-based solutions.)
(We can increase i/o timeouts to compensate if really necessary.)
> My goal here is to replace an existing cluster of 5 nodes using clvmd + dlm
> + corosync to access a shared VG of 6 TB containing around 300 LVs.
>
> The current solution is working fine but I find using dlm + corosync "just"
> for locking a bit overkill.
I agree.
Dave
prev parent reply other threads:[~2017-04-20 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 16:14 [linux-lvm] ubuntu xenial + lvmlockd Charles Koprowski
2017-04-18 16:00 ` David Teigland
2017-04-20 9:26 ` Charles Koprowski
2017-04-20 15:40 ` David Teigland [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=20170420154048.GA29033@redhat.com \
--to=teigland@redhat.com \
--cc=cko@audaxis.com \
--cc=linux-lvm@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.