[Pacemaker] [PATCH] ping RA: Improvement of the logging

[Yoshihiko SATO]

Hi Andrew,

I confirmed.

When debug="true", pingRA is output the execution log of attrd_updater.

>>>>> And, because the ping failure is not normal, the log level is more
>>>>> than
>>>>> warning.
>>>>
>>>> It depends on how you want to use the scores.
I understand.
The log of attrd_updater is not necessary without depending on the usage of the score.
So, I want to distinguish from the log of attrd_updater.

please, your comment.

Best Regards,
Yoshihiko SATO

(2010/05/13 09:34), Yoshihiko SATO wrote:
> Hi Andrew,
>
>> done
>> http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/c47e0dd67e3f
>
> Thanks.
>
> Best Regards,
> Yoshihiko SATO
>
> (2010/05/12 21:22), Andrew Beekhof wrote:
>> done
>> http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/c47e0dd67e3f
>>
>> On Tue, May 11, 2010 at 4:59 AM, Yoshihiko SATO
>> <satoyoshi at intellilink.co.jp> wrote:
>>> Hi, Andrew
>>>
>>>> I've pushed this instead:
>>>> http://hg.clusterlabs.org/pacemaker/1.1/rev/e8624c181a3f
>>>
>>> Thank you!
>>>
>>> I want you to do the backport for stable-1.0.
>>>
>>> Regards,
>>> Yoshihiko SATO
>>>
>>>
>>> (2010/05/10 18:04), Andrew Beekhof wrote:
>>>>
>>>> 2010/5/7 Yoshihiko SATO<satoyoshi at intellilink.co.jp>:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I improved logging of the ping RA.
>>>>>
>>>>> Now, when the ping command failed (rc=1), log is not output.
>>>>> I want to output to the log which target failed.
>>>>
>>>> I disabled it originally because people complained it was too noisy.
>>>> Especially if, as is common for ping/pingd, you have a short
>>>> monitoring interval.
>>>>
>>>>> When two or more targets exist (host_list="target1 target2
>>>>> target3"), the
>>>>> failure target can be confirmed at once.
>>>>
>>>> I don't understand this bit.
>>>>
>>>>> And, because the ping failure is not normal, the log level is more
>>>>> than
>>>>> warning.
>>>>
>>>> It depends on how you want to use the scores.
>>>> If you just want to make sure you can see one of the listed nodes,
>>>> then its not really a warning.
>>>>
>>>>> I would like to hear any opinion.
>>>>
>>>> I've pushed this instead:
>>>> http://hg.clusterlabs.org/pacemaker/1.1/rev/e8624c181a3f
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>> _______________________________________________
>> 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
>>
>
>
> _______________________________________________
> 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
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ping.patch
Type: text/x-patch
Size: 653 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100513/976b2380/attachment-0003.bin>