From: Eric Ren <zren@suse.com>
To: David Teigland <teigland@redhat.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] The benefits of lvmlockd over clvmd?
Date: Tue, 9 Jan 2018 11:15:24 +0800 [thread overview]
Message-ID: <bc1ccc58-1771-183b-2d40-1d8b198fb8b5@suse.com> (raw)
Hi David,
Regarding the question of the subject, I can think of three main
benefits of lvmlockd over clvmd:
- lvmlockd supports two cluster locking plugins: dlm and sanlock.
sanlock plugin can supports up to ~2000 nodes
that benefits LVM usage in big virtulizaton/storage cluster, while dlm
plugin fits HA clsuter.
- lvmlockd has better design than clvmd. clvmd is command-line level
based locking system, which means the
whole LVM software will get hang if any LVM command gets dead-locking
issue. However, lvmlockd is *resources* based
cluster locking. The resources to protect is VG and LV so that the
deadlock issue will be isolated inside the resource and
operations on other VG/LV can still proceed.
- lvmlockd can work with lvmetad.
But, I may be wrong in some points. Could you please help correct me and
complete the benefit list?
Thanks!
Eric
next reply other threads:[~2018-01-09 3:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 3:15 Eric Ren [this message]
2018-01-09 16:06 ` [linux-lvm] The benefits of lvmlockd over clvmd? David Teigland
2018-01-10 7:11 ` Eric Ren
2018-01-10 9:36 ` Zdenek Kabelac
2018-01-10 14:42 ` Eric Ren
2018-01-10 15:35 ` Zdenek Kabelac
2018-01-10 17:25 ` David Teigland
2018-01-10 16:45 ` 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=bc1ccc58-1771-183b-2d40-1d8b198fb8b5@suse.com \
--to=zren@suse.com \
--cc=linux-lvm@redhat.com \
--cc=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).