public inbox for [email protected]
help / color / mirror / Atom feedFrom: Stefan Knecht <[email protected]>
To: Rory Campbell-Lange <[email protected]>
Cc: Daniele Varrazzo <[email protected]>
Cc: [email protected]
Subject: Re: psycopg3: a first report
Date: Mon, 30 Mar 2020 16:14:59 +0700
Message-ID: <CAP50yQ9WSB6s_rfXe2S0V-8H8ByCRNSw6ninrGdn5NgLzWZ8bA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CA+mi_8ZH-feQP0+k_j7_joygE=hMZCFnaNMv8Z1KCLKB9YLb0w@mail.gmail.com>
<CAP50yQ_Mt=RtR0sXYoazJTuarphR1Kv8A6YTevCMiv+xZeD9=Q@mail.gmail.com>
<[email protected]>
Rory, this is about established connections, not new connections - psycopg2
already offers a connection timeout, but that is a different thing. I don't
want to drift too far off topic - but we are already using pgbouncer, and
the problem isn't detected by it, either. I'm not a developer but I believe
the problem is the generic nature of some blocking socket calls, which may
hang under some odd circumstances, and they remain hanging until some odd
ssl timeout is reached (15 minutes+ which is a very long time for any
application to be hanging in limbo, but more so for our own monitoring
tools which are written in Python).
Having the client provide general handling for in-flight timeouts would be
the overall best solution imho.
On Mon, Mar 30, 2020 at 2:48 PM Rory Campbell-Lange <[email protected]>
wrote:
> On 30/03/20, Stefan Knecht ([email protected]) wrote:
> > If I may, one thing that has been a constant troublemaker for us -
> running
> > primarily on AWS - is timeouts.
>
> If the issue is disappearing hosts or general connectivity problems,
> isn't that problem best dealt with by pg_bouncer?
>
> https://www.pgbouncer.org/config.html#connection-sanity-checks-timeouts
>
> Specifically you may wish to refer to server_connect_timeout.
>
> Rory
>
>
--
//
zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
Visit us at zztat.net | @zztat_oracle | fb.me/zztat | zztat.net/blog/
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: psycopg3: a first report
In-Reply-To: <CAP50yQ9WSB6s_rfXe2S0V-8H8ByCRNSw6ninrGdn5NgLzWZ8bA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox