I’m building a two node cluster (three nodes in future), and I’d like to prevent nodes from start whenever other nodes does not join the cluster. However, I don’t like the idea of fencing a node is not part of the cluster in an uncontrolled way when other node is forming a new cluster (let’s say, while patching the system). I’ve found a nice way to do so by configuring clean_start to 0 and post_join_delay to “-1". With this configuration fence daemon will not try to fence the nodes out of the cluster and will wait until the rest of nodes join the cluster in this status:
[root jimenez1 admin]# group_tool
type level name id state
fence 0 default 00010001 JOIN_START_WAIT
dlm 1 rgmanager 00020001 none
[root jimenez1 admin]# clustat
Cluster Status for ext_test @ Tue Dec 29 15:01:54 2009
Member Status: Quorate
Member Name ID Status
------ ---- ---- ------
hb-jimenez1 1 Online, Local
hb-jimenez2 2 Offline
This is the behavior I want, however, there is still a problem. I’d like to be able to manually start the cluster in that node by means of a command or something like that. I’ve seen in the past I could use fence_tool with –c option to leave the JOIN_START_WAIT status and let the cluster start with only one node. However, this options does not seem to be available in my version (I’m using RHEL 5.3) and cman version cman-2.0.115-1.el5_4.9.
With this configuration, is there any way to start the cluster manually in only one node without reconfiguring the cluster? Is there any other configuration that allows me to have the same functionality?
F. Hoffmann-La Roche Ltd.
Global Informatics Group Infrastructure
Phone: +34 91 305 97 87
Confidentiality Note: This message is intended only for the use of the named recipient(s) and may contain confidential and/or proprietary information. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorized use of the information contained in this message is prohibited.