[Pacemaker] Make pacemaker retry failed resources

[Gareth Davis]

Sure:

http://www.linux-ha.org/doc/dev-guides/ra-dev-guide.html

On start failing my RA returns

$OCF_ERR_GENERIC

There doesn't seem to be any other choice. I looked at OCF_NOT_RUNNING,
but this is exclusively for the monitor action.

Monitor does return OCF_NOT_RUNNING.

What seems to happen is

Monitor - OCF_NOT_RUNNING
start - OCF_ERR_GENERIC

And then it stops trying, I would like it just to  keep trying to start
the resource for ever.

Gareth

On 09/05/2012 17:33, "Dejan Muhamedagic" <dejanmm at fastmail.fm> wrote:

>Hi,
>
>On Wed, May 09, 2012 at 03:23:43PM +0000, Gareth Davis wrote:
>> Hi, 
>> 
>> This actually cross posted from
>> 
>>http://serverfault.com/questions/387425/make-pacemaker-retry-failed-resou
>>rc
>> es
>> 
>> I would like to get pacemaker to retry starting my resource
>> 
>> 	primitive Imq ocf:example:imq \
>>    	  op monitor on-fail="restart" interval="10s" \
>>    	  op start interval="0" timeout="60s" on-fail="restart" \
>>    	  meta failure-timeout="30s"
>> 
>> Note that this resource is pinned to the first node via
>> 
>> 	location location_Imq Imq inf: vm1
>> 	location location_Imq1 Imq -inf: vm2
>> 
>> Currently if I break something that stops this resource from starting
>>the
>> failure count returns INFINITY and stops attempting to restart the
>>service.
>> 
>> I would like to never give up on the resource so that once the
>> intermittent issue clears its self the resource restarts and resumes
>> service.
>
>That depends entirely on the exit codes returned by the RA. This
>seems to be your own, right? Did you check the Resource agents
>developers guide?
>
>Thanks,
>
>Dejan
>
>> Using pacemaker 1.0 on CentOS.
>> 
>> Gareth
>> 
>> 
>> 
>> 
>> 
>> 
>> This message contains confidential information and may be privileged.
>>If you are not the intended recipient, please notify the sender and
>>delete the message immediately.
>> 
>> ip.access Ltd, registration number 3400157, Building 2020,
>> Cambourne Business Park, Cambourne, Cambridge CB23 6DW, United Kingdom
>> 
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> 
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>
>_______________________________________________
>Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>Project Home: http://www.clusterlabs.org
>Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>Bugs: http://bugs.clusterlabs.org






This message contains confidential information and may be privileged. If you are not the intended recipient, please notify the sender and delete the message immediately.

ip.access Ltd, registration number 3400157, Building 2020, 
Cambourne Business Park, Cambourne, Cambridge CB23 6DW, United Kingdom