On 8/27/07, Reza Behroozi <[EMAIL PROTECTED]> wrote: > >If less than half of your nodes are online, your cluster looses its > >quorum .... the default no_quorum_policy is to stop all resources. > >Unless you change the quorum_policy to ignore I think there is no way > >to get the resources started on the last remaining node. > > if last node dont start so what's diff between 2 node and 3 node?
In a two-node heartbeat cluster the nodes do always have quorum, otherwise with two nodes there would be no failover possible in case of a server crash relying on quorum decissions only ... for that reason STONITH is really recommended for two-node clusters to prevent a split-brain situation. With three nodes it is safe to decide one node is down in case two nodes agree that they can't contact the third node. And the third (separated) node does a shutdown of its local cluster resources (or does not failover resources from other nodes) because it's more likely there is a problem with itself that caused the separation than with all the other nodes .... if it really happens that the majority of the cluster nodes are down (and it is unable to resolve this situation with STONITH) it is time for an administrator to decide if it is safe for the last remaining node to start the resources, because heartbeat can't decide. Regards, Andreas > > >Which version of HA? Does crm_mon show any failed actions? > ver2 > no-node 1 and 2 become offline and node 3 is online but dont start resource > > thanks for reply > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
