Hi Jerome > The name of the servers are as follows: Nomen and Rubric. > > Let us start when Nomen owns all resources and its status states > "running(dc)". When I stop heartbeat on Nomen, Rubric takes over all the > resources and its status turns into "running(dc)". This is good as this is > what I had hoped that it will do. > > When I start heartbeat back on Nomen, it takes all the resource away from > Rubric. However, it leaves Rubric in "running(dc)" status and Nomen's status > just states "running". There are two issues here that I see. > > 1) I do not want Nomen to take the resources as this means that the > resources will be bounced.
This happens because of your rsc_location constraint. You normally want your resource to be on "nomen", so if the cluster can, it will run it there. <rsc_location id="fdstest" rsc="Directory_Server"> <rule id="prefered_fdstest" score="100" boolean_op="or"> <expression attribute="#uname" id="9e5698e0-8b07-43aa-b852-398fbe6bb909" operation="eq" value="nomen.esri.com"/> </rule> </rsc_location> If you want the resource to stick to its current location even when the preferred node comes back, look into the meta-attribute "resource-stickiness". Read http://www.linux-ha.org/ScoreCalculation > 2) I would like to have the Quorum or "running(dc)" where the resources are. You can't move the dc role manually. And you do not have to bother which machine is the dc. It is totally fine having resources on a node which is not the dc. The current dc stays dc until it is shutdown or separated from the cluster in some manner. > To continue, when I stop heartbeat on Rubric, the "running(dc)" status goes > over to Nomen. I then start heartbeat in Rubric and all resources as well as > the "running(dc)" stays with Nomen. Moreover, the resources are not bounced > at all. Also due to your rsc_location. The resource is where you configured it (on nomen), so why move it around? Regards Dominik _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
