On Wed, Apr 21, 2010 at 5:07 PM, Schaefer, Diane E
wrote:
>>> Hi,
> Yes, I am saying that if a resource (R1) is taking a long time to start and
> another resource (R2) monitor action returns a not running, it will not be
> restarted until the first stuck resource returns or in my case times out.
>
>> Hi,
>> I have a resource that sometimes can take 10 minutes to start after
>> a failure due to log records that need to be sync'd. (my own OCF)
>>
>> I noticed while the start action was being performed, if other
>>
>> resources in my cluster report a "not running", no restart will
On Fri, Apr 16, 2010 at 02:28:26PM -0500, Schaefer, Diane E wrote:
> Hi,
> I have a resource that sometimes can take 10 minutes to start after
> a failure due to log records that need to be sync'd. (my own OCF)
>
> I noticed while the start action was being performed, if other
> resources i
>> Actually this RA waits for the sync to complete. If it takes longer than
>> the allotted time-out, Pacemaker SIGTERM/SIGKILLs it. The issue is if it
>> can never complete in the allotted time frame...
>Then make the timeout longer?
I could make the timeout longer, although I'm not sure
On Mon, Apr 19, 2010 at 2:29 PM, Schaefer, Diane E
wrote:
>>> Hi,
>
>>>
>
>>> ? I have a resource that sometimes can take 10 minutes to start after a
>
>>> failure due to log records that need to be sync?d. (my own OCF)? I
>>> noticed
>
>>> while the start action was being performed, if other reso
>> Hi,
>>
>> ? I have a resource that sometimes can take 10 minutes to start after a
>> failure due to log records that need to be sync?d. (my own OCF)? I noticed
>> while the start action was being performed, if other resources in my cluster
>> report a ?not running?, no restart will be attem
On Fri, Apr 16, 2010 at 9:28 PM, Schaefer, Diane E
wrote:
> Hi,
>
> I have a resource that sometimes can take 10 minutes to start after a
> failure due to log records that need to be sync’d. (my own OCF) I noticed
> while the start action was being performed, if other resources in my cluster
>
Hi,
I have a resource that sometimes can take 10 minutes to start after a failure
due to log records that need to be sync'd. (my own OCF) I noticed while the
start action was being performed, if other resources in my cluster report a
"not running", no restart will be attempted until my long r
