<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace"><div class="gmail_default"><br></div><div class="gmail_default">...</div><div class="gmail_default">2019-02-09 05:17:35: pid 19275: LOG: PCP process with pid: 9642 exit with SUCCESS.</div><div class="gmail_default">2019-02-09 05:17:35: pid 19275: LOG: PCP process with pid: 9642 exits with status 0</div><div class="gmail_default">2019-02-09 05:17:35: pid 19275: LOG: forked new pcp worker, pid=9644 socket=7</div><div class="gmail_default">2019-02-09 05:17:35: pid 19275: LOG: PCP process with pid: 9644 exit with SUCCESS.</div><div class="gmail_default">2019-02-09 05:17:35: pid 19275: LOG: PCP process with pid: 9644 exits with status 0</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: forked new pcp worker, pid=9647 socket=7</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: PCP process with pid: 9647 exit with SUCCESS.</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: PCP process with pid: 9647 exits with status 0</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: forked new pcp worker, pid=9649 socket=7</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: PCP process with pid: 9649 exit with SUCCESS.</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: PCP process with pid: 9649 exits with status 0</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: forked new pcp worker, pid=9651 socket=7</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: PCP process with pid: 9651 exit with SUCCESS.</div><div class="gmail_default">2019-02-09 05:17:40: pid 19275: LOG: PCP process with pid: 9651 exits with status 0</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: forked new pcp worker, pid=9655 socket=7</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: PCP process with pid: 9655 exit with SUCCESS.</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: PCP process with pid: 9655 exits with status 0</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: forked new pcp worker, pid=9657 socket=7</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: PCP process with pid: 9657 exit with SUCCESS.</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: PCP process with pid: 9657 exits with status 0</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: forked new pcp worker, pid=9659 socket=7</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: PCP process with pid: 9659 exit with SUCCESS.</div><div class="gmail_default">2019-02-09 05:17:46: pid 19275: LOG: PCP process with pid: 9659 exits with status 0</div><div class="gmail_default">2019-02-09 05:17:47: pid 19276: LOG: received degenerate backend request for node_id: 1 from pid [19276]</div><div class="gmail_default">2019-02-09 05:17:47: pid 19402: LOG: new IPC connection received</div><br class="gmail-Apple-interchange-newline"></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 18, 2019 at 12:47 PM Pierre Timmermans <<a href="mailto:ptim007@yahoo.com">ptim007@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_-3548791530064573299ydp3f63e7a9yahoo-style-wrap" style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:16px"><div><div>Alexander, you should give more logs from the production set-up, in particular the lines before this one : </div><div><br></div><div><br></div><div><span><span style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif">2019-02-09 05:17:47: pid 19402: LOG: watchdog received the failover</span><br clear="none" style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif"><span style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif">> >> > > command from local pgpool-II on IPC interface</span><br clear="none" style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif"><span style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif">> >> > > 2019-02-09 05:17:47: pid 19402: LOG: watchdog is processing the</span><br clear="none" style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif"><span style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif">> >> failover</span></span><br></div><div><br></div><div><span><span style="color:rgb(0,0,0);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:16px">Maybe there is an indication of what caused the failover. </span></span><br></div><div><br></div><div class="gmail-m_-3548791530064573299ydp3f63e7a9signature">Pierre</div></div>
<div><br></div><div><br></div>
</div><div id="gmail-m_-3548791530064573299ydpe82c5ef8yahoo_quoted_0799630009" class="gmail-m_-3548791530064573299ydpe82c5ef8yahoo_quoted">
<div style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px;color:rgb(38,40,42)">
<div>
On Monday, February 18, 2019, 3:00:22 PM GMT+1, Alexander Dorogensky <<a href="mailto:amazinglifetime@gmail.com" target="_blank">amazinglifetime@gmail.com</a>> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="gmail-m_-3548791530064573299ydpe82c5ef8yiv7666916253"><div><div dir="ltr"><div class="gmail-m_-3548791530064573299ydpe82c5ef8yiv7666916253gmail_default" style="font-family:"courier new",monospace">Any idea why pgpool doesn't retry?</div></div><br clear="none"><div class="gmail-m_-3548791530064573299ydpe82c5ef8yiv7666916253gmail_quote"><div class="gmail-m_-3548791530064573299ydpe82c5ef8yiv7666916253yqt6843868097" id="gmail-m_-3548791530064573299ydpe82c5ef8yiv7666916253yqtfd17826"><div class="gmail-m_-3548791530064573299ydpe82c5ef8yiv7666916253gmail_attr" dir="ltr">On Sun, Feb 17, 2019 at 6:19 PM Bo Peng <<a shape="rect" href="mailto:pengbo@sraoss.co.jp" rel="nofollow" target="_blank">pengbo@sraoss.co.jp</a>> wrote:<br clear="none"></div><blockquote class="gmail-m_-3548791530064573299ydpe82c5ef8yiv7666916253gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br clear="none">
<br clear="none">
I confirmed your pgpool.conf, you set <br clear="none">
<br clear="none">
health_check_max_retries = 16<br clear="none">
<br clear="none">
So I think the following result is correct. <br clear="none">
<br clear="none">
> >> > psql -c 'pgpool show health_check_max_retries'<br clear="none">
> >> > health_check_max_retries<br clear="none">
> >> > --------------------------<br clear="none">
> >> > 16<br clear="none">
> >> > (1 row)<br clear="none">
<br clear="none">
On Fri, 15 Feb 2019 07:12:56 -0500<br clear="none">
Alexander Dorogensky <<a shape="rect" href="mailto:amazinglifetime@gmail.com" rel="nofollow" target="_blank">amazinglifetime@gmail.com</a>> wrote:<br clear="none">
<br clear="none">
> Hi,<br clear="none">
> <br clear="none">
> Do you have any ideas what’s going on?<br clear="none">
> <br clear="none">
> On Mon, Feb 11, 2019 at 8:30 PM Alexander Dorogensky <<br clear="none">
> <a shape="rect" href="mailto:amazinglifetime@gmail.com" rel="nofollow" target="_blank">amazinglifetime@gmail.com</a>> wrote:<br clear="none">
> <br clear="none">
> > Pgpool.conf from one of the app nodes is attached<br clear="none">
> ><br clear="none">
> > Thanks<br clear="none">
> ><br clear="none">
> > On Mon, Feb 11, 2019 at 6:59 PM Bo Peng <<a shape="rect" href="mailto:pengbo@sraoss.co.jp" rel="nofollow" target="_blank">pengbo@sraoss.co.jp</a>> wrote:<br clear="none">
> ><br clear="none">
> >> Hi,<br clear="none">
> >><br clear="none">
> >> On Mon, 11 Feb 2019 15:32:55 -0600<br clear="none">
> >> Alexander Dorogensky <<a shape="rect" href="mailto:amazinglifetime@gmail.com" rel="nofollow" target="_blank">amazinglifetime@gmail.com</a>> wrote:<br clear="none">
> >><br clear="none">
> >> > I'm running 4 app (pgpool) nodes (3.6.10) and 2 db (postgres) nodes<br clear="none">
> >> (9.6.9)<br clear="none">
> >> > primary/standby configuration with streaming replication. All 6 nodes<br clear="none">
> >> are<br clear="none">
> >> > separate machines.<br clear="none">
> >> ><br clear="none">
> >> > A client has had too many failovers caused by the flaky network and in<br clear="none">
> >> an<br clear="none">
> >> > effort to remedy the issue I set the following parameters<br clear="none">
> >> ><br clear="none">
> >> > health_check_max_retries = 7<br clear="none">
> >> > health_check_retry_delay = 15<br clear="none">
> >> ><br clear="none">
> >> > Now, I have the client's environment and a lab environment to reproduce<br clear="none">
> >> the<br clear="none">
> >> > issue. Pgpool configuration and the version are identical.<br clear="none">
> >> ><br clear="none">
> >> > To simulate a flaky network, I use iptables to deny postgres<br clear="none">
> >> connections to<br clear="none">
> >> > one of the db nodes and see that pgpool on all app nodes is trying to<br clear="none">
> >> > reconnect according to the configured number of retries and retry delay,<br clear="none">
> >> ><br clear="none">
> >> > > i.e.<br clear="none">
> >> > > 2019-02-11 14:22:51: pid 7825: LOG: failed to connect to PostgreSQL<br clear="none">
> >> > > server on "<a shape="rect" href="http://10.0.10.133:5433" rel="nofollow" target="_blank">10.0.10.133:5433</a>", getsockopt() detected error "No route<br clear="none">
> >> to<br clear="none">
> >> > > host"<br clear="none">
> >> > > ...<br clear="none">
> >> > > 2019-02-11 14:23:23: pid 6458: LOG: health checking retry count 1<br clear="none">
> >> > > ...<br clear="none">
> >> > > 2019-02-11 14:23:38: pid 6458: LOG: health checking retry count 2<br clear="none">
> >> > > ...<br clear="none">
> >> > > 2019-02-11 14:42:45: pid 6458: LOG: health checking retry count 3<br clear="none">
> >> > > ...<br clear="none">
> >> > > 2019-02-11 14:43:00: pid 6458: LOG: health checking retry count 4<br clear="none">
> >> > > ...<br clear="none">
> >> > > 2019-02-11 14:43:15: pid 6458: LOG: health checking retry count 5<br clear="none">
> >> > > ...<br clear="none">
> >> > > 2019-02-11 14:43:30: pid 6458: LOG: health checking retry count 6<br clear="none">
> >> > > ...<br clear="none">
> >> > > 2019-02-11 14:43:30: pid 6460: LOG: failover request from local<br clear="none">
> >> pgpool-II<br clear="none">
> >> > > node received on IPC interface is forwarded to master watchdog node "<br clear="none">
> >> > > <a shape="rect" href="http://172.20.20.173:5432" rel="nofollow" target="_blank">172.20.20.173:5432</a>"<br clear="none">
> >> > > 2019-02-11 14:43:30: pid 4565: LOG: watchdog received the failover<br clear="none">
> >> > > command from remote pgpool-II node "<a shape="rect" href="http://172.20.20.172:5432" rel="nofollow" target="_blank">172.20.20.172:5432</a>"<br clear="none">
> >> > > ...<br clear="none">
> >> > > 2019-02-11 14:43:30: pid 4563: LOG: execute command:<br clear="none">
> >> > > /etc/pgpool-II/failover.sh 0 10.0.10.133 5433 /opt/redsky/db/data 1 0<br clear="none">
> >> > > 10.0.10.134 1 5433 /opt/redsky/db/data<br clear="none">
> >> > ><br clear="none">
> >> > > However, in the client's environment failover gets initiated before<br clear="none">
> >> the<br clear="none">
> >> > configured number of retries, i.e.<br clear="none">
> >> ><br clear="none">
> >> > 2019-02-09 05:17:47: pid 19402: LOG: watchdog received the failover<br clear="none">
> >> > > command from local pgpool-II on IPC interface<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19402: LOG: watchdog is processing the<br clear="none">
> >> failover<br clear="none">
> >> > > command [DEGENERATE_BACKEND_REQUEST] received from local pgpool-II on<br clear="none">
> >> IPC<br clear="none">
> >> > > interface<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19402: LOG: forwarding the failover request<br clear="none">
> >> > > [DEGENERATE_BACKEND_REQUEST] to all alive nodes<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19402: DETAIL: watchdog cluster currently<br clear="none">
> >> has 3<br clear="none">
> >> > > connected remote nodes<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19276: ERROR: unable to read data from DB<br clear="none">
> >> node 1<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19276: DETAIL: socket read failed with an<br clear="none">
> >> error<br clear="none">
> >> > > "Success"<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19400: LOG: Pgpool-II parent process has<br clear="none">
> >> > > received failover request<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19402: LOG: new IPC connection received<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19402: LOG: received the failover command<br clear="none">
> >> lock<br clear="none">
> >> > > request from local pgpool-II on IPC interface<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19402: LOG: local pgpool-II node "<br clear="none">
> >> > > <a shape="rect" href="http://10.15.35.35:5432" rel="nofollow" target="_blank">10.15.35.35:5432</a>" is requesting to become a lock holder for failover<br clear="none">
> >> ID:<br clear="none">
> >> > > 19880<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19402: LOG: local pgpool-II node "<br clear="none">
> >> > > <a shape="rect" href="http://10.15.35.35:5432" rel="nofollow" target="_blank">10.15.35.35:5432</a>" is the lock holder<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19400: LOG: starting degeneration. shutdown<br clear="none">
> >> host<br clear="none">
> >> > > 10.38.135.137(5433)<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19400: LOG: Restart all children<br clear="none">
> >> > > 2019-02-09 05:17:47: pid 19400: LOG: execute command:<br clear="none">
> >> > > /etc/pgpool-II/failover.sh 1 10.38.135.137 5433 /opt/redsky/db/data 0<br clear="none">
> >> 0<br clear="none">
> >> > > 10.15.35.39 1 5433 /opt/redsky/db/data<br clear="none">
> >> > ><br clear="none">
> >> > ><br clear="none">
> >> > I ran the following command on all app nodes<br clear="none">
> >> ><br clear="none">
> >> > psql -c 'pgpool show health_check_max_retries'<br clear="none">
> >> > health_check_max_retries<br clear="none">
> >> > --------------------------<br clear="none">
> >> > 16<br clear="none">
> >> > (1 row)<br clear="none">
> >> ><br clear="none">
> >> > and the number is different from what I have in the configuration file..<br clear="none">
> >> > It's more than 1 though and I expect it to be honored.<br clear="none">
> >><br clear="none">
> >> I could not reproduce this issue by using pgpool_setup.<br clear="none">
> >> Could you share the whole pgpool.conf?<br clear="none">
> >><br clear="none">
> >> > Can you guys help me out? I'm out of ideas..<br clear="none">
> >> ><br clear="none">
> >> > pgpool-II-pg96-3.6.10-1pgdg.rhel6.x86_64<br clear="none">
> >><br clear="none">
> >><br clear="none">
> >> --<br clear="none">
> >> Bo Peng <<a shape="rect" href="mailto:pengbo@sraoss.co.jp" rel="nofollow" target="_blank">pengbo@sraoss.co.jp</a>><br clear="none">
> >> SRA OSS, Inc. Japan<br clear="none">
> >><br clear="none">
> >><br clear="none">
<br clear="none">
<br clear="none">
-- <br clear="none">
Bo Peng <<a shape="rect" href="mailto:pengbo@sraoss.co.jp" rel="nofollow" target="_blank">pengbo@sraoss.co.jp</a>><br clear="none">
SRA OSS, Inc. Japan<br clear="none">
<br clear="none">
</blockquote></div></div></div></div><div class="gmail-m_-3548791530064573299ydpe82c5ef8yqt6843868097" id="gmail-m_-3548791530064573299ydpe82c5ef8yqtfd69431">_______________________________________________<br clear="none">pgpool-general mailing list<br clear="none"><a shape="rect" href="mailto:pgpool-general@pgpool.net" rel="nofollow" target="_blank">pgpool-general@pgpool.net</a><br clear="none"><a shape="rect" href="http://www.pgpool.net/mailman/listinfo/pgpool-general" rel="nofollow" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br clear="none"></div></div>
</div>
</div></div></blockquote></div>