On 7 Feb 2014, at 8:54 pm, Frank Brendel wrote:
>
>> Its somewhat inferred in the description of cluster-recheck-interval
>>
>>cluster-recheck-interval = time [15min]
>>Polling interval for time based changes to options, resource
>> parameters and constraints.
>>
>>
Its somewhat inferred in the description of cluster-recheck-interval
cluster-recheck-interval = time [15min]
Polling interval for time based changes to options, resource
parameters and constraints.
The Cluster is primarily event driven, however the configuratio
On 3 Feb 2014, at 9:40 pm, Frank Brendel wrote:
> I've solved the problem.
>
> When I set cluster-recheck-interval to a value less than failure-timeout
> it works.
>
> Is this an expected behavior?
Yes.
>
> This is not documented anywhere.
Its somewhat inferred in the description of clust
I've solved the problem.
When I set cluster-recheck-interval to a value less than failure-timeout
it works.
Is this an expected behavior?
This is not documented anywhere.
Neither here
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Clusters_from_Scratch/index.html
nor here
h
No one with an idea?
Or can someone tell me if it is even possible?
Thanks
Frank
Am 23.01.2014 10:50, schrieb Frank Brendel:
> Hi list,
>
> I have some trouble configuring a resource that is allowed to fail
> once in two minutes.
> The documentation states that I have to configure migration-th
Hi list,
I have some trouble configuring a resource that is allowed to fail once
in two minutes.
The documentation states that I have to configure migration-threshold
and failure-timeout to achieve this.
Here is the configuration for the resource.
# pcs config
Cluster Name: mycluster
Corosync N
