From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman/man qdisk.5
Date: 14 Nov 2007 16:37:12 -0000 [thread overview]
Message-ID: <20071114163712.15788.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: lhh at sourceware.org 2007-11-14 16:37:12
Modified files:
cman/man : qdisk.5
Log message:
Fix #317561 - pass 1
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/qdisk.5.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.3.2.4&r2=1.3.2.5
--- cluster/cman/man/qdisk.5 2007/03/20 19:37:04 1.3.2.4
+++ cluster/cman/man/qdisk.5 2007/11/14 16:37:11 1.3.2.5
@@ -1,6 +1,6 @@
-.TH "QDisk" "5" "20 Feb 2007" "" "Cluster Quorum Disk"
+.TH "QDisk" "5" "06 Sep 2007" "" "Cluster Quorum Disk"
.SH "NAME"
-QDisk 1.2 \- a disk-based quorum daemon for CMAN / Linux-Cluster
+QDisk 1.2.1 \- a disk-based quorum daemon for CMAN / Linux-Cluster
.SH "1. Overview"
.SH "1.1 Problem"
In some situations, it may be necessary or desirable to sustain
@@ -73,7 +73,8 @@
* Cluster node IDs must be statically configured in cluster.conf and
must be numbered from 1..16 (there can be gaps, of course).
-* Cluster node votes should be more or less equal.
+* Cluster nodes must have one vote each. The effects of nodes having
+any number of votes besides 1 has not been explored.
* CMAN must be running before the qdisk program can operate in full
capacity. If CMAN is not running, qdisk will wait for it.
@@ -83,10 +84,10 @@
failure + load spike situation.
* For 'all-but-one' failure operation, the total number of votes assigned
-to the quorum device should be equal to or greater than the total number
-of node-votes in the cluster. While it is possible to assign only one
-(or a few) votes to the quorum device, the effects of doing so have not
-been explored.
+to the quorum device should be equal to the number of nodes in the cluster
+minus 1. For example, if you have 3 nodes in the cluster, each node should
+get one vote and qdisk should get 2 votes. This then lets the cluster
+operate without qdisk if all nodes are online for testing and other purposes.
* For 'tiebreaker' operation in a two-node cluster, unset CMAN's two_node
flag (or set it to 0), set CMAN's expected votes to '3', set each node's
@@ -338,6 +339,13 @@
on every block device found, comparing the label against the specified
label. This is useful in configurations where the block device name
differs on a per-node basis.
+
+.in 9
+\fIcman_label\fP\fB="\fPmylabel\fB"/>\fP
+.in 12
+This overrides the label advertised to CMAN if present. If specified,
+the quorum daemon will register with this name instead of the actual
+device name.
.in 8
\fB...>\fP
.in 0
next reply other threads:[~2007-11-14 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 16:37 lhh [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-12 6:18 [Cluster-devel] cluster/cman/man qdisk.5 fabbione
2007-11-14 17:14 lhh
2007-01-26 21:12 lhh
2006-10-03 18:07 lhh
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=20071114163712.15788.qmail@sourceware.org \
--to=lhh@sourceware.org \
/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.