Hi, On Mon, March 9, 2009 6:42 pm, Pavel Georgiev wrote: > I`m running heartbeat 2.99 + pacemaker 1.0. I have migration-threshold=2 > and failure-timeout=600s. When I simulate 2 resource failures per server, > the resource is migrated to the next node (as expected). When all servers > eligible for running the resource reach migration-threshold failures (2), > the resource is not started anywhere (as expected), but I would expect > that after the timeout is expeired, the resource would automatically be > started on the node. Is this possible or in such case there is a need for > manual intervention (cibadmin -B does the job)?
Have a look at the output of "/usr/lib/heartbeat/crmd metadata" and search for "cluster_recheck_interval" ... and add it to your crm_config. I think Andrew already added a patch to pacemaker so the cluster_recheck_interval is enabled by default and can be changed during runtime ... in the next release. > > On another subject - is there another way of identifying nodes in the > constraints section besides by uname (like IP of the first network > interaface)? hmm ... the node uuid is a builtin attribute to identify a node, another way could be to add a custom attribute using attrd_updater. Regards, Andreas -- : Andreas Kurz : LINBIT | Your Way to High Availability : Tel +43-1-8178292-64, Fax +43-1-8178292-82 : : http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. This e-mail is solely for use by the intended recipient(s). Information contained in this e-mail and its attachments may be confidential, privileged or copyrighted. If you are not the intended recipient you are hereby formally notified that any use, copying, disclosure or distribution of the contents of this e-mail, in whole or in part, is prohibited. Also please notify immediately the sender by return e-mail and delete this e-mail from your system. Thank you for your co-operation. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
