Redhat Cluster is a nice HA product. I have been implementing it for a while now, lecturing about it, and yes – I like it. But like any other software product, it has few flaws and issues which you should take under consideration – especially when you create custom “agents” – plugins to control (start/stop/status)…
I encountered an interesting bug/feature of RHCS on RHEL4. A snip of my configuration looks like this: <resources> <fs device=”/dev/mapper/mpath6p1″ force_fsck=”1″ force_umount=”1″ fstype=”ext3″ name=”share_prd” mountpint=”/share_prd” options=”” self_fence=”0″ fsid=”02001″/> <nfsexport name=”nfs export4″/> <nfsclient name=”all ro” target=”192.168.0.0/255.255.255.0″ options=”ro,no_root_sqush,sync”/> <nfsclient name=”app1″ target=”app1″ options=”rw,no_root_squash,sync”/> </resources> <service autostart=”1″ domain=”prd” name=”prd” nfslock=”1″> <fs ref=”share_prd”> <nfsexport ref=”nfs export 4″> <nfsclient ref=”all ro”/>…
I have been struggling with RH Cluster 4 with VMware fencing device. This was also a good experiance with qdiskd, the Disk Quorum directive and utilization. I have several conclusions out of this experience. First, the configuration, as is: <?xml version=”1.0″?> <cluster alias=”alpha_cluster” config_version=”17″ name=”alpha_cluster”> <quorumd interval=”1″ label=”Qdisk1″ min_score=”3″ tko=”10″ votes=”3″> <heuristic interval=”2″ program=”ping vm-server…
