On Wed, Jul 30, 2008 at 19:18, daniel peess <[EMAIL PROTECTED]> wrote: > hello andreas, > > On Wed, Jul 30, 2008 at 11:04:10AM +0200, Andreas Kurz wrote: >> Ok .. I see. Try to set the 'default-resource-stickiness' to a >> positive value and give each of your groups a different 'priority'. >> That should do the trick. > > setting the 'default-resource-stickiness' to a positive value now prevents > the restart behavior when a node returns, thanks. > but this is only half of a workaround for the problem below. > > this doesn't help if you crash/standby/stop a node. > resources that were running on this node are pushing away > other resources, although both of their scores are equal/unset. > if other free nodes are available the failing resource should start there, > and if none are available shouldn't start at all. > > instead heartbeat restarts resources depending on the colocation > constraints, although those should just distribute the resources across all > nodes. > > again, all groups shall be treated equal if they have the same score, > the failure of one shall never affect other ones. > IMHO this is a bug.
then please submit one _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
