[pgpool-general: 366] Re: Random Connection Failures and processes in status D
donmartio at larkos.de
Mon Apr 23 17:02:54 JST 2012
Hello and hurray,
the new release 3.1.3 seems to fix our problem. I think it's somehow
related to the syslog problem since we
have used it. We didn't have any connection failures but the processes
in D (deadlock?!?). They
are now gone.
This is great. Thank you... great work.
Am 30.03.2012 09:57, schrieb DonMartio:
> Hello again,
> since i can't find similiar issues except this one:
> i think it's somehow my fault. I'll do some trial and error with the
> config params.
> The client_idle_limit may is helpfull here even if the client is not
> connected anymore.
> Just for proper understanding. Does this mean that a client is
> disconnected even if
> there is running an 'expensive query'?
> Am 29.03.2012 17:21, schrieb DonMartio:
>> we are evaluating pgpool the first time because we hit a serious
>> connection Problem
>> (Increasing virtual xen maschines leads to increasing max_connections).
>> Running 2 Postres 9 Instances for failover reasons we thought it
>> would be a good idea
>> to run pgpool in master slave mode.
>> First tests ran well but we recognized a serious increase of loadavg
>> on the pgpool maschine.
>> The reason is an increasing count of pgpool processes running in
>> status D.
>> Netstat tells us that they are in CLOSE_WAIT. We can't kill them. We
>> have to
>> restart pgpool.
>> What ist going wrong here?
>> Any hint appreciated
>> Greetings so far
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
> pgpool-general mailing list
> pgpool-general at pgpool.net
More information about the pgpool-general