[pgpool-general: 2886] Re: [pgpool-hackers: 529] Bugs with PgPool 3.3.3.1 _ PostgreSQL 9.3.4 configuration

Yugo Nagata nagata at sraoss.co.jp
Wed May 28 11:57:27 JST 2014


(moved to pgpool-general)

Hi,

On Tue, 27 May 2014 16:45:24 +0000
"Burgess, Freddie" <FBurgess at Radiantblue.com> wrote:

> The log file attachment came from the master server running streaming replication.
> 
> Now, we are having major issues with pgpool. We have a cluster of processing VM's that connected thru the pgpool VM to the master/slave servers. These processing VM's serve up pages to our UI via Hibernate queries. If we disconnect these processing server connections and bounce pgpool, then all of the processing server connections are reestablished with no issues, but if we bounce any one of the processing VM servers while pgpool is up and then try to reconnect, we cannot. The processing servers just hang indefinitely. 
> 
> When I checked the connected sessions, there was about forty sessions connected to the pgpool VM. We have max_connections on the master/slave databases set to 100, and we you can see from our pgpool.conf setting that we should be allowing 128 connections.

Sorry, I'm confused and not sure what operation you did exactly. However, 
I see pgpool.conf as below:

# - Pool size -

num_init_children = 32
                                   # Number of pools
                                   # (change requires restart)
max_pool = 4
                                   # Number of connections per pool
                                   # (change requires restart)


By this configuration, pgpool can process only 32 conections, not 128 = 32*4.

====
num_init_children

The number of preforked pgpool-II server processes. Default is 32. 
num_init_children is also the concurrent connections limit to pgpool-II
from clients
(http://www.pgpool.net/docs/latest/pgpool-en.html#NUM_INIT_CHILDREN)
===

> 
> I'm not sure what is going on, but we had to re-route the processing server connections directly to the master database server, so that our mission-critical app will work,
> 
> Are there any special setting that you are aware of when running pgpool with Hibernate and PostgreSQL 9.3.4 and PostGIS 2.1.1
> 
> thanks
> 
> 
> ________________________________________
> From: Yugo Nagata [nagata at sraoss.co.jp]
> Sent: Tuesday, May 27, 2014 4:45 AM
> To: Burgess, Freddie
> Cc: pgpool-hackers at pgpool.net
> Subject: Re: [pgpool-hackers: 529] Bugs with PgPool 3.3.3.1 _ PostgreSQL 9.3.4 configuration
> 
> Hi,
> 
> On Wed, 21 May 2014 19:06:46 +0000
> "Burgess, Freddie" <FBurgess at Radiantblue.com> wrote:
> 
> > We installed installer-pg93-3.3.3.tar.gz and we are running into two major problems.
> >
> > 1.)  The pgpoolAdmin URL http://<serverIP>/pgpoolAdmin/login.php<http://<ServerIP>/pgpoolAdmin/login.php> interface locks up everyday, and has to be bounced every morning.
> 
> The pgpoolAdmin problem soule be answered by Anzai.
> 
> > 2.) On the master database log we are getting the error: portal "pgpool_error_portal" does not exist
> 
> Could you please show me pgpool.conf, and full log messages of both pgpool and backends?
> 
> >
> > Any assistance will be greatly appreciated.
> >
> > thanks
> >
> 
> 
> --
> Yugo Nagata <nagata at sraoss.co.jp>


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


More information about the pgpool-general mailing list