Hello, On 01/06/2012 06:14 PM, erkan yanar wrote: > > 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.
If the resource is not ready be promoted it should have no promotion score ... is this the mysql RA coming with the resource-agents package or a home-grown RA? > > 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? Even if it would be ok to promote such an instance, why not increasing the promote timeout to a "fixed" safe value? Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > > > Regards > Erkan > > > > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
