[pgpool-general: 1269] Re: Connections stuck in CLOSE_WAIT
ishii at postgresql.org
Mon Dec 31 09:39:20 JST 2012
> I have recently updated pgpool from 3.2.1 to the latest HEAD in the
> 3_2_STABLE branch (mainly for
> 22e045e2f362bb007a72ef1651ed2da897e3aa86) . Since then, I notice that
> sometimes connections to pgpool are stuck in a half-closed state which
> also causes pgpool to keep the connections to the backend postgres
> boxes open.
> The connections from the application to pgpool are stuck in CLOSE_WAIT state.
> Any idea what may be causing this, and more importantly, how to stop it?
That means pgpool does not close the socket connected to by your
applications. Is it possible to attach debugger to such that pgpool
process to see what pgpool is doing?
SRA OSS, Inc. Japan
> The problem with this is that the pgpool process keeps the connection
> open and doesn't accept new connections which will cause it to use up
> all slots quite quickly at which point it can't be connected to any
> I can forcibly close the connection on the postgres end
> (pg_terminate_backend()), but I've had instances where pgpool thought
> this was an abnormal termination and subsequently marked the node as
> Sensational AG
> Giesshübelstrasse 62c, Postfach 1966, 8021 Zürich
> Tel. +41 43 544 09 60, Mobile +41 79 341 01 99
> info at sensational.ch, http://www.sensational.ch
> pgpool-general mailing list
> pgpool-general at pgpool.net
More information about the pgpool-general