Bug status import should happen outside transaction block

Bug #172825 reported by Graham Binns
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Björn Tillenius

Bug Description

At present bug watches updates are pulled in from remote sources within the transaction block within which those updates will be applied to the database. This is a bad idea since a long-running import process could lead to the transaction staying open for far too long. We have scripts which will kill such transactions and which will, as a result, kill the checkwatches process should such a situation occur.

The imports and updates should happen separately, that is to say that imports should be done before the updates are applied to the database, with database updates happening within a transaction block and the imports happening outside of it.

Graham Binns (gmb)
Changed in malone:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Björn Tillenius (bjornt) wrote :

With the refactoring of ExternalBugTracker, I think this should be quite easy to do now.

Changed in malone:
milestone: none → 1.2.3
Changed in malone:
assignee: nobody → bjornt
Changed in malone:
status: Confirmed → In Progress
Revision history for this message
Björn Tillenius (bjornt) wrote :

Fixed in RF5888.

Changed in malone:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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