[pgpool-general: 1688] Re: [PGPOOL] when the connection is full, watchdog works abnormally

[Yugo Nagata]

Hi Kuo Huang,

Unfortunately, there are no way to discriminate normal client's connections 
from watchdog's connection. Larger num_init_children, wd_life_point and smaller
wd_interval may prevent the problem somewhat. The next major version, pgpool-II
3.3, will support a new monitoring method which uses UDP heartbeat packets
instead of queries such like 'SELECT 1' to resolve the problem.

Yugo Nagata 

On Tue, 07 May 2013 18:00:07 +0900 (JST)
Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> 長田君
> 
> この件対応願います。
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese: http://www.sraoss.co.jp
> 
> From: Kuo Huang (黃種國) <Kuo.Huang at quantatw.com>
> Subject: [PGPOOL] when the connection is full, watchdog works abnormally
> Date: Fri, 3 May 2013 08:13:13 +0000
> Message-ID: <2A73E4E458EC9843B413CD9EC82C3535A42DA180 at Mailbx04.quanta.corp>
> 
> > Hi,
> > 
> > There are few questions about the watchdog and num_init_children of config parameter.
> > When the connection number reach the number of num_init_children, the watchdog will be failed because select 1 is failed, and then VIP will be transfer to another pgpool
> > Are there any mechanism to separate the different connections from normal clients or watchdog?
> > EX:
> > Pgpool_1(VIP): the num_init_children is 32
> > Pgppol_2: the num_init_children is 32
> > There are 32 DB client that connected to Pgpool_1, and the log of Pgpool_1 shows “wd_lifecheck: lifecheck failed 3 times, pgpool 1 (IP:5432) seems not to be working”,
> > and then VIP will transfer to Pgpool_2.
> > 
> > 
> > Best Regards
> > Kuo
> > 


-- 
Yugo Nagata <nagata at sraoss.co.jp>