[pgpool-general: 287] Re: idle stale connections hanging around

[Tatsuo Ishii]

> Greetings,
> I'm running pgpool-II-3.1.2 on a 64bit Linux system.  I have the
> following set in my pgpool.conf:
> 
> child_life_time = 300
> child_max_connections = 990
> connection_life_time = 3
> client_idle_limit = 30
> 
> I thought this meant that a client connection that was idle for at
> least 30 seconds would be automatically terminated, yet I see a large
> number of pgpool 'idle' processes that are days old:
> postgres 13886 28335  0 Mar04 ?        00:00:00 pgpool: lfriedman
> nightly 10.31.96.104(59242) idle
> postgres 17068 28335  0 Mar22 ?        00:00:08 pgpool: lfriedman
> nightly 10.31.96.232(43232) idle
> postgres 17501 28335  0 Mar22 ?        00:00:01 pgpool: lfriedman
> inventory 10.31.96.111(54649) idle
> postgres 17521 28335  0 Mar22 ?        00:00:07 pgpool: lfriedman
> nightly 10.31.96.232(43237) idle
> postgres 17981 28335  0 Mar13 ?        00:00:02 pgpool: lfriedman
> nightly 10.31.45.25(54973) idle
> postgres 18152 28335  0 Mar13 ?        00:00:02 pgpool: lfriedman
> nightly 10.31.96.156(49366) idle
> postgres 18629 28335  0 Mar13 ?        00:00:01 pgpool: lfriedman
> nightly 10.31.97.219(54997) idle
> postgres 19510 28335  0 Mar13 ?        00:00:00 pgpool: lfriedman
> nightly 10.31.97.218(58289) idle
> 
> Many of these are from clients that aren't even powered on, so they're
> clearly not doing anything to keep the connection non-idle.  Is this a
> bug?

These are new to me. Can you attach gdb one of those processes to get
a backtrace?

> Is there something that I can do to gracefully terminate these
> connections (such that pgpool will spawn a new unused process)?

If you are sure that the pgpool child is in idle, kill -9 should work.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp