Hi,
I’m using Heartbeat 2.99.1 and Pacemaker 1.0.2. I have configured a resource with the migration-threshold=2 and failure-timeout=60s. When I simulate 2 resource failures per server, the resource is automatically migrated to the other node (docucluster04) as excepted. group_color: virtual-ip-alfresco allocation score on docucluster03: -1000000 group_color: virtual-ip-alfresco allocation score on docucluster04: 0 native_color: virtual-ip-alfresco allocation score on docucluster03: -1000000 native_color: virtual-ip-alfresco allocation score on docucluster04: 0 After 60s (migration-threshold) I can see the following scores, but the resource is not started back on the original node (docucluster03). group_color: virtual-ip-alfresco allocation score on docucluster03: 1000000 group_color: virtual-ip-alfresco allocation score on docucluster04: 0 native_color: virtual-ip-alfresco allocation score on docucluster03: 1000000 native_color: virtual-ip-alfresco allocation score on docucluster04: 0 I have tried to set the ‘ cluster-recheck-interval’ option, this tells the cluster to periodically recalculate the ideal state of the cluster … but the resource isn’t still migrated automatically back on the original node (docucluster03) After executing cibadmin –B (bump) the resource is migrated to docucluster03. Anyone idea what to do for a automatically migration after expiring the failure-timeout? Best regards, Koen _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
