>>> kevins7189 <[email protected]> schrieb am 15.09.2011 um 15:22 in Nachricht <[email protected]>:
> First time builder of a openais/pacemaker based cluster. Been using an old > heartbeat 2.1 cluster for years and it has been 100% reliable and works > every time, simple two node file server. > Trying to use the new software, having some issues. > > Firstly, is there a way in a two node cluster to make it so when a rebooted > node comes up it does not disturb the services already running on the other > node. I've seen reports of this issue but no solutions, maybe not searching If "disturbing" means "rebalancing of resources", "stickiness" is the word you may be looking for. > for the right terms correctly. > Basically my setup is dbrd backed storage between two nodes, and running nfs > and mysql. Failover almost never works when a node locks up for some > reason, or other disturbances in network, but seems to be OK when a > functional shutdown is made. This is running on Dell 2950 servers. I have Distinguish between "node locks up", "network locks up" and "resource minitor times out" > been unsuccessful getting the dracs to talk IPMI over LAN, guessing because > I don't want to waste the two onboard nics just to make it work. We are using SBD via SAN here and the HP iLO (hpilo/hpwdt) to reset the nodes. > > Here is my configuration, is there anything here that is not correct for a > two node cluster with drbd/nfs/mysql? I followed the > drbd/nfs/mysql/postgesql guide, but eliminated postgesql and the need for > two drbd partitions because they are not needed. My expectation is that if > one node goes down, the other node takes over, that's it. > > Here is my config if someone would be so kind as to check it out. > > node node0-1 \ > attributes standby="off" > node node0-2 \ > attributes standby="off" > primitive drbd_nfs ocf:linbit:drbd \ > params drbd_resource="node0-drbd" \ > op monitor interval="15s" > primitive fs_nfs ocf:heartbeat:Filesystem \ > params device="/dev/drbd0" directory="/pub" fstype="ext3" \ > op start interval="0" timeout="60" \ > op stop interval="0" timeout="120" \ > meta target-role="Started" > primitive ip1 ocf:heartbeat:IPaddr2 \ > params ip="192.168.1.2" nic="eth0" \ > op monitor interval="5s" > primitive ip1arp ocf:heartbeat:SendArp \ > params ip="192.168.1.2" nic="eth0" > primitive mysql ocf:heartbeat:mysql \ > params binary="/usr/local/mysql/bin/mysqld_safe" > config="/etc/my.cnf" datadir="/usr/local/mysql/mysql-data" > socket="/var/run/mysql/mysql.sock" pid="/var/run/mysql/mysqld.pid" \ > op start interval="0" timeout="120" \ > op stop interval="0" timeout="120" \ > op monitor interval="60" timeout="30" depth="0" \ > meta target-role="Started" > primitive nfs lsb:nfsserver \ > meta target-role="Started" > group HAServices ip1 ip1arp fs_nfs nfs mysql \ > meta target-role="Started" > ms ms_drbd_nfs drbd_nfs \ > meta master-max="1" master-node-max="1" clone-max="2" > clone-node-max="1" notify="true" > colocation ms-drbd-nfs-with-haservices inf: ms_drbd_nfs:Master HAServices > order fs-nfs-before-nfs inf: fs_nfs:start nfs:start > order ip-before-arp inf: ip1:start ip1arp:start > order ip-before-ms-drbd-nfs inf: ip1:start ms_drbd_nfs:promote > order ms-drbd-nfs-before-fs-nfs inf: ms_drbd_nfs:promote fs_nfs:start > order ms-drbd-nfs-before-mysql inf: ms_drbd_nfs:promote mysql:start > property $id="cib-bootstrap-options" \ > dc-version="--" \ > cluster-infrastructure="openais" \ > expected-quorum-votes="2" \ > stonith-enabled="false" \ > no-quorum-policy="ignore" \ > cluster-recheck-interval="0" > rsc_defaults $id="rsc-options" \ > resource-stickiness="100" > > Also, I could have swore I read a post where someone was able to get STONITH > to work by ssh'ing to the other node and issue an ipmi shutdown that way, I > think that would solve my issue if I really need STONITH. > > thanks in advance for any assistance. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
