[pgpool-general: 4262] Re: pgpool doesn't split the connections between the backends

[Tatsuo Ishii]

>  Hello Everyone,  
>   Happy holidays!  Can anyone assist on how to set-up pgpool to distribute connections between the backend database nodes , in other words to split the connection count between them. Currently it seems that every connection to pgpool in turn is a connection to every database backend.  
>   Our setup is:  
>  
>  
>  
>  /----- postgresql - master  pgpool--------postgresql - slave 1  
>  
>  
>  
>  \-----postgresql - slave 2  
>   When I check the connections I get 60 to pgpool from the Tomcat client which pools that much and 60 to each of the database servers.  How can I configure it so I have 
> 20 per backend database node.  
>   As this would be a really heavy loaded system with many DB connections we want to limit the connections to not more than 900 per server, as postgresql advise not to have more than 1000 connections per database, because performance radically drops.  When the system gets under load and the connections reach 900 the backends start to reports "too many clients already", which triggers a "degeneration" of the node, which in pgpool terms means to take out the node from balancing and mark it with status "3".  Isn't there a way to just keep 300 connections per server and a total of 900 from the client to pgpool only?  

I think if you could turn off the connection pooling of Tomcat, you
could achieve the goal (you can set num_init_children below 1000).

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp