[pgpool-hackers: 1555] Re: Subject=Re: Re: Re: Allow to access to pgpool while doing health checking

[James Sewell]

Hello,

What about triggering a replication lag check whenever a node passes a
health check?

Cheers,


James Sewell,
PostgreSQL Team Lead / Solutions Architect
______________________________________


Level 2, 50 Queen St, Melbourne VIC 3000

*P *(+61) 3 8370 8000  *W* www.lisasoft.com  *F *(+61) 3 8370 8099


On Mon, May 9, 2016 at 3:44 PM, Tatsuo Ishii <ishii at postgresql.org> wrote:

> > Hey All,
> >
> > This looks like a great step forward for PGPool.
> >
> > One question - would it be possible to set health_check_max_retries to a
> > value which means it will just keep retrying?
> >
> >
> > This way a node which was inactive for a longer period could still return
> > to service once it started responding.
> >
> > Or perhaps there is another, better way to deal with this?
>
> Hum. At the moment I can't think of a reason why this does not
> work. One thing I'm worrying is, the node which starts to respond is
> actually in a good state or not. If it's an outdated standby, users
> may get outdated data before pgpool notices that the standby delay is
> too much. Though I have to admit that this is an existing problem even
> if you do not try the large health_check_max_retries value. We need
> more rigorous checking with failback?
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>

-- 


------------------------------
The contents of this email are confidential and may be subject to legal or 
professional privilege and copyright. No representation is made that this 
email is free of viruses or other defects. If you have received this 
communication in error, you may not copy or distribute any part of it or 
otherwise disclose its contents to anyone. Please advise the sender of your 
incorrect receipt of this correspondence.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20160511/4d9d0653/attachment.html>