Dejan Muhamedagic <dejanmm <at> fastmail.fm> writes: > > Hi, > > On Mon, Dec 06, 2010 at 05:02:48AM +0000, Preeti Jain wrote: > > Lars Ellenberg <lars.ellenberg <at> linbit.com> writes: > > > > > > > > On Sun, Dec 05, 2010 at 02:02:25PM +0800, Bin Chen(sunwen_ling) wrote: > > > > Hi Dan, Thanks so much for your explanation! > > > > > > > > I am wondering is there an easy way to change the default behavior? Can I > > > > set the score dynamically when the resource is going up(set the currently > > > > running node higher than other node)? > > > > I just don't want the resource to be migrated unnecessarily. The result I for the same configuration above mentioned by Bin i am getting an error in my > > log file on node B when node A comes up(either after network failure or system > > reboot) regarding "resource appears to be active on two nodes" and having same > > score(of default resource stickiness INFINITY/1000 on both value same > > error) so > > choose node A, > > any help.... > > I guess that you don't have fencing (stonith) setup and that the > node A on boot thinks that its alone in the cluster (delay on > a network switch?) so it starts the resource. > > Thanks, > > Dejan
Thanks for your reply, Yes you are right i do not have stonith enabled in my setup so that means i need to setup fencing for this trouble if so then how to do it and what i need, like any hardware is required for this setup..... or is there any other way to avoid it.... Regards Preeti > > > > > > > > _______________________________________________ > > Linux-HA mailing list > > Linux-HA <at> lists.linux-ha.org > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ > Linux-HA mailing list > Linux-HA <at> lists.linux-ha.org > 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
