Jerome Yanga wrote: > Dominik, > > Thank you much. Adding "resource-stickiness" and getting rid of the > constraint helped a lot. The resources does not go back to Nomen anymore > when it's heartbeat is started again (resources stays with Rubric). > However, the resources still gets bounced once Nomen joins the cluster. Is > there any way to keep the resources from bouncing when Nomen rejoins the > cluster?
Please share your current configuration. > I have also observed another issue. As you have seen in my cib.xml, I have > created a group called Directory_Server. In this group, there are three > resources, namely: VIP, ECAS and FDS_Admin. If I manually turn off any of > these resources, I would like the group resource, Directory_Server, to > failover to the other node. Is there a configuration that will do this? > Currently, if one of three resources goes down it stays down and the rest > continues running. All three resources will need to be up and running for > our applications to work properly. Sounds like you're not doing any resource monitoring. Read up on that and configure it. The ScoreCalculation page might be handy to understand how things work: http://www.linux-ha.org/ScoreCalculation Regards Dominik _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
