In an other customer setup we decided to set a resource to status "unmanaged" when it has to do some special work which should not be interrupted. After the replication (in our case redloogs in a backup db) we set the resource to be managed again.
I never have tried to change already triggered timeouts. Kind regards Fabian 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. > > 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 > > > > > _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
