On Fri, Nov 26, 2010 at 12:58 PM, Andrew Beekhof <and...@beekhof.net> wrote: > On Fri, Nov 26, 2010 at 12:46 PM, Bharath Khandelwal > <bharath.khandel...@opticalfusion.net> wrote: >> In Heartbeat 2 cluster of four nodes how to stop auto failback: >> >> as in cib i am having default resource stickiness —- INFINITY >> >> no-quorum-policy --- ignore , and no constraint. >> >> 1- IF i stop heartbeat on node A failover happens and ip resource shifts to >> node B stays >> there if i start heartbeat on node A, but >> >> 2- When i give init 6 on node A again failover happens and ip resource >> shifts to node B but as node A again joins the cluster after reboot >> (heartbeat is on at run level services boot time) ip resource fails back to >> node A which is not expected > > either you're starting it at boot time or you have a location > constraint with INFINITY for the original node. > or its something to do with colocation
In cib there is no constraint, if possible then i want it through default setting of cluster.othrewise how should i write constraint for schenario mentioned below. > >> >> 3- Node A goes down then with default setting and without constraint which >> node will get the ip resource ????.what will be the default behaviour of >> cluster in such schenario. > > its based on strcmp() of the hostnames and/or how many other resources > they have running > >> 4- if node B gets resource in above case then when if i make node A up and >> node B down then resource is failing back on node A which is not expected >> either it should move to node C or D which is desired > > why? As per requirement of TL i need this sequence : I want sequence should be like this : 1---if A goes down B should take over2-- if A is up B is down C should take over not fail back to Node A (as it is happening now)means i want my cluster should go in sequence like A then B then C then D and again there should be a cycle starting from A B C D...... >> >> if any solution then please help….. >> >> Thanks _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
