[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Linux-cluster] Info on quorum rename on rhcs 5.8



Hello,
I saw some discussions in the past regarding the subject, such as:
https://www.redhat.com/archives/cluster-devel/2011-September/msg00027.html

My config is with an rhcs based on  rhel 5.8 two nodes + quorum disk cluster and
cman-2.0.115-96.el5_8.3
openais-0.80.6-36.el5_8.2
rgmanager-2.0.52-28.el5_8.2

I'm evaluating SAN migration from a storage array to another,
including data disks and quorum disks, limiting downtime and
considering pros&cons of several scenarios.
One of the problems is quorum disk moving.

I start in a situation where the nodes are seeing both the SANs and
cluster data disks (in HA-LVM config) are already on new storage while
quorum not.

My test approach is this:
- stop qdiskd on first node and wait for stabilization
second node becomes master
- stop qdiskd on second node and wait for stabilization

- cluster maintains quorum (2 votes instead of expected 3 for each server)

- format the new quorum lun with a different label
- change cluster.conf accordingly and update/distribute the config with
<quorumd device="/dev/mapper/mpnquorum" interval="5" label="nquorum"
log_facility="local4" log_level="7" tko="16" votes="1">
- start qdiskd on first node and wait for stabilization
it becomes master
- start qdiskd on second node and wait for stabilization

>From qdiskd point view all is gong well but openais shows:
Sep 28 11:21:00 noracs1 openais[7671]: [CMAN ] unable to re-register
quorum device: device names do not match

Complete messages in qdiskd.log I set up are these, after start of
qdiskd on the two nodes:

Sep 28 11:16:35 noracs2 qdiskd[9422]: <debug> Heuristic: 'ping -c1 -w1
10.4.5.250' score=1 interval=2 tko=200
Sep 28 11:16:35 noracs2 qdiskd[9422]: <debug> 1 heuristics loaded
Sep 28 11:16:35 noracs2 qdiskd[9422]: <debug> Quorum Daemon: 1
heuristics, 5 interval, 16 tko, 1 votes
Sep 28 11:16:35 noracs2 qdiskd[9422]: <debug> Run Flags: 00000031
Sep 28 11:16:35 noracs2 qdiskd[9422]: <info> Quorum Partition:
/dev/dm-6 Label: nquorum
Sep 28 11:16:35 noracs2 qdiskd[9423]: <info> Quorum Daemon Initializing
Sep 28 11:16:35 noracs2 qdiskd[9423]: <debug> I/O Size: 512  Page Size: 4096
Sep 28 11:16:36 noracs2 qdiskd[9423]: <info> Heuristic: 'ping -c1 -w1
10.4.5.250' UP
Sep 28 11:17:55 noracs2 qdiskd[9423]: <info> Initial score 1/1
Sep 28 11:17:55 noracs2 qdiskd[9423]: <info> Initialization complete
Sep 28 11:17:55 noracs2 openais[7653]: [CMAN ] unable to re-register
quorum device: device names do not match
Sep 28 11:17:55 noracs2 qdiskd[9423]: <notice> Score sufficient for
master operation (1/1; required=1); upgrading
Sep 28 11:18:05 noracs2 qdiskd[9423]: <debug> Making bid for master
Sep 28 11:18:40 noracs2 qdiskd[9423]: <info> Assuming master role
Sep 28 11:20:05 noracs2 qdiskd[9423]: <debug> Node 1 is UP

Sep 28 11:19:40 noracs1 qdiskd[3779]: <debug> Heuristic: 'ping -c1 -w1
10.4.5.250' score=1 interval=2 tko=200
Sep 28 11:19:40 noracs1 qdiskd[3779]: <debug> 1 heuristics loaded
Sep 28 11:19:40 noracs1 qdiskd[3779]: <debug> Quorum Daemon: 1
heuristics, 5 interval, 16 tko, 1 votes
Sep 28 11:19:40 noracs1 qdiskd[3779]: <debug> Run Flags: 00000031
Sep 28 11:19:40 noracs1 qdiskd[3779]: <info> Quorum Partition:
/dev/dm-5 Label: nquorum
Sep 28 11:19:40 noracs1 qdiskd[3780]: <info> Quorum Daemon Initializing
Sep 28 11:19:40 noracs1 qdiskd[3780]: <debug> I/O Size: 512  Page Size: 4096
Sep 28 11:19:41 noracs1 qdiskd[3780]: <info> Heuristic: 'ping -c1 -w1
10.4.5.250' UP
Sep 28 11:20:05 noracs1 qdiskd[3780]: <debug> Node 2 is UP
Sep 28 11:20:10 noracs1 qdiskd[3780]: <info> Node 2 is the master
Sep 28 11:21:00 noracs1 qdiskd[3780]: <info> Initial score 1/1
Sep 28 11:21:00 noracs1 qdiskd[3780]: <info> Initialization complete
Sep 28 11:21:00 noracs1 openais[7671]: [CMAN ] unable to re-register
quorum device: device names do not match
Sep 28 11:21:00 noracs1 qdiskd[3780]: <notice> Score sufficient for
master operation (1/1; required=1); upgrading

status reported is this:
[root noracs1 ~]# cman_tool status
Version: 6.2.0
Config Version: 9
Cluster Name: clnacs
Cluster Id: 6477
Cluster Member: Yes
Cluster Generation: 56
Membership state: Cluster-Member
Nodes: 2
Expected votes: 3
Quorum device votes: 1
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 9
Flags: Dirty
Ports Bound: 0 177
Node name: iclnacs1
Node ID: 1
Multicast addresses: 239.192.25.102
Node addresses: 192.168.16.42

[root noracs2 ~]# cman_tool status
Version: 6.2.0
Config Version: 9
Cluster Name: clnacs
Cluster Id: 6477
Cluster Member: Yes
Cluster Generation: 56
Membership state: Cluster-Member
Nodes: 2
Expected votes: 3
Quorum device votes: 1
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 9
Flags: Dirty
Ports Bound: 0 177
Node name: iclnacs2
Node ID: 2
Multicast addresses: 239.192.25.102
Node addresses: 192.168.16.43

So it seems ok.
This cluster is for testing with one service running now on node 1 so
I can shutdown the node 2 and verify if it maintains correctly  the
quorum...

But from an approach point of view are my steps correct/supported in
my 5.8 config?
Did it change anything in later versions such as rh el 6.3 or Fedora 17?
Thanks in advance

Gianluca


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]