Moin, Im having the issue, that promoting a master can run into the promote timeout. After that, the resource is stopped and started as a slave.
In my example it is a mysql resource, where promoting is going to wait for any replication lag to be applied. This could last a very long time. There are some thoughts on that issue: 1. Dynamically increase the timeout with cibadmin. I havent tested that yet. Would this work? 2. op-fail=ignore With ignore, the resource is not restarted. But I don't like that approach. Is there an intelligent approach to dynamically change the timeout while promoting? Or is there a better approach anyway? Regards Erkan -- über den grenzen muß die freiheit wohl wolkenlos sein _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
