Hello, On 12/04/2011 09:29 PM, Muhammad Sharfuddin wrote: > This cluster reboots(fenced) both nodes, if I disconnects network of any > nodes(simulating network failure).
Completely loss of network is indistinguishable for a cluster node to a dead peer. > > I want that if any node disconnects from network, resources running on > that node should be moved/migrate > to the other node(network connected node) Use ping RA for connectivity checks and use location constraints to move resources according to network connectivity (to external ping targets) > > How can I prevent this cluster to reboot(fence) the healthy node(i.e the > node whose network is up/available/connected). Multiple-failure scenarios are challenging and possible solutions for a cluster are limited. With enough effort by an administrator every cluster can be "tested to death". You can only minimize the possibility of a split-brain: * use redundant cluster communication paths (limited to two with corosync) * at least one communication path is direct connected * use a quorum node If you are using a network connected fencing device use this network also for cluster communication. To prevent stonith death matches use power-off as stonith action or/and don't start cluster services on system startup. Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > > I am using following STONITH resource > primitive sbd_stonith stonith:external/sbd \ > meta target-role="Started" \ > op monitor interval="3000" timeout="120" \ > op start interval="0" timeout="120" \ > op stop interval="0" timeout="120" \ > params > sbd_device="/dev/disk/by-id/scsi-360080e50002377b8000002ff4e4bc873" > > > -- > Regards, > > Muhammad Sharfuddin > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
