[pgpool-general: 2461] Re: wd_escalation_command exit code
Sergey Arlashin
sergeyarl.maillist at gmail.com
Tue Jan 21 16:19:49 JST 2014
Thank you for the patch. I'll try it a bit later.
It seems there is another weird thing about wd_escalation.
Even if if_up_cmd fails to assign failover ip to the node and fails with exit code 1 I still see:
pgpool[16969]: wd_escalation: escalating to master pgpool
pgpool[16969]: wd_escalation: escalated to master pgpool successfully
pgpool[16969]: wd_init: start watchdog
As the result I have not working cluster with no errors in logs whatsoever.
On Jan 21, 2014, at 9:43 AM, Yugo Nagata <nagata at sraoss.co.jp> wrote:
> Hi,
>
> No, it's not bug.
> pgpool just ignore wd_escalation command's exit code.
>
> However, if you would like the feature, could you try the patch attached?
>
>
> On Mon, 20 Jan 2014 23:29:15 +0400
> Sergey Arlashin <sergeyarl.maillist at gmail.com> wrote:
>
>> Hi!
>>
>> When wd_escalation_command fails with exit code '1' pgpool does not log any errors. It logs the following messages instead:
>>
>> pgpool[3384]: wd_escalation: escalating to master pgpool
>> pgpool[3384]: wd_escalation: escalated to master pgpool successfully
>>
>> Is it a bug?
>>
>> --
>> Best regards,
>> Sergey Arlashin
>> _______________________________________________
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>
>
> --
> Yugo Nagata <nagata at sraoss.co.jp>
> <excalation_cmd.patch>
More information about the pgpool-general
mailing list