Scripts should run with a database transaction timeout

Bug #704698 reported by Stuart Bishop on 2011-01-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

Currently there is no protection for scripts holding open transactions for a long time. Sometimes, this is hours.

We need timeouts such as the webapp has causing scripts to abort if they hold open a transaction longer than a configurable time limit.

Robert Collins (lifeless) wrote :

We have seen recent operational issues related to this, so its critical : we will avoid various timeout OOPS if we do this. We need to be cautious about the deployment of it - needs to be easy to turn off because many scripts likely fail the test right now.

Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
Robert Collins (lifeless) wrote :

Oh, and I suggest an initial timeout of 20 seconds.

tags: added: timeout

It might be nice to do this on jtv's recent script feature scope
stuff? Then it can be set dynamically per script.

Aaron Bentley (abentley) wrote :

We have a transaction killer today, but it (currently) isn't aggressive enough to solve this bug. Robert reports he envisioned per-script policies, because otherwise many scripts would fail today.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers