Launchpad itself

pages hitting disconnection error took 21 seconds to fail

Bug #846162 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Expired
High
Unassigned

Bug Description

This suggests our pg connection timeout is 20 seconds or something huge; we should set that to our remaining page duration (similar to how we set the statement timeout).

Revision history for this message
Stuart Bishop (stub) wrote :

Connection failure should happen instantly, as there is nothing listening on the target socket. Firewall rules on production could block the rejection packets.

Retry handling might be kicking in, where if the database is unavailable the request is retried a few times. This may or may not be a good thing.

Revision history for this message
Stuart Bishop (stub) wrote :

If the database is unavailable, the 503 page is returned immediately. We know the database is unavailable, as the pgbouncer proxy is shutdown during the fastdowntime db updates.

I'm going to flag this as incomplete. It might have been fixed when we made Launchpad return 503 error pages. If not, we need more information such as an OOPS. Perhaps the page was going to timeout anyway, and a long query interrupted by the outage?

Changed in launchpad:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Launchpad itself because there has been no activity for 60 days.]

Changed in launchpad:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.