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 > > > want is, when the resource is running in one node, regardless of other > > > node > > > status, and as long as currently node is up and running, the resouce > > > shouldn't be migrated. > > > > > > I don't know if I set the location constraints works, because what I want > > > is > > > some sort of dynamic feature, not restrict the resource to some permanent > > > ones. > > > > > > Can you please suggest? > > > > set a positive (but not infinity) default resource stickiness > > > 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 > Regards > Preeti > > > > _______________________________________________ > 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
