[ClusterLabs] Antw: Re: [Question] About a change of crm_failcount.
Ulrich.Windl at rz.uni-regensburg.de
Mon Feb 6 03:44:38 EST 2017
>>> Ken Gaillot <kgaillot at redhat.com> schrieb am 02.02.2017 um 19:33 in Nachricht
<91a83571-9930-94fd-e635-96283067105c at redhat.com>:
> On 02/02/2017 12:23 PM, renayama19661014 at ybb.ne.jp wrote:
>> Hi All,
>> By the next correction, the user was not able to set a value except zero in
>> - [Fix: tools: implement crm_failcount command-line options correctly]
>> However, pgsql RA sets INFINITY in a script.
>> ocf_exit_reason "My data is newer than new master's one. New master's
> location : $master_baseline"
>> exec_with_retry 0 $CRM_FAILCOUNT -r $OCF_RESOURCE_INSTANCE -U $NODENAME -v
>> return $OCF_ERR_GENERIC
>> There seems to be the influence only in pgsql somehow or other.
>> Can you revise it to set a value except zero in crm_failcount?
>> We make modifications to use crm_attribute in pgsql RA if we cannot revise
>> Best Regards,
>> Hideo Yamauchi.
> Hmm, I didn't realize that was used. I changed it because it's not a
> good idea to set fail-count without also changing last-failure and
> having a failed op in the LRM history. I'll have to think about what the
> best alternative is.
The question also is whether the RA can acieve the same effect otherwise. I thought CRM sets the failcount, not the RA...
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
More information about the Users