[pgpool-hackers: 3362] Re: Behavior of resigned master watchdog node

Muhammad Usama m.usama at gmail.com
Fri Aug 2 18:48:46 JST 2019


Hi Ishii-San

On Fri, Aug 2, 2019 at 10:25 AM Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> Hi Usama,
>
> In your commit:
>
> https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=33df0d33df1ce701f07fecaeef5b87a2707c08f2
>
> "the master watchdog node should resign from master responsibilities
> if the primary backend node gets into quarantine state on that."
>
> While testing this feature, I noticed that the master watchdog node
> resign from master responsibilities as expected in this case. However
> none of standby nodes gets promoted to new primary. As a result,
> there's no primary node any more after the master watchdog resign.
>
> This is not very good because users cannot


This is not at all expected behavior, Can you please share the logs or
steps to reproduce the issue.
I will look into this on priority.

Thanks
Best Regards
Muhammad Usama



> issue write queries
> anymore. Is this intended?
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190802/2cda2b4b/attachment.html>


More information about the pgpool-hackers mailing list