Deadlock between UI and importer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Jeroen T. Vermeulen |
Bug Description
On 2008-12-23 we observed a deadlock between the importer and the translation UI, leading to an error from the import script and two timeout reports from the app servers. (The affected UI user reported retrying once when the server took too long to respond).
The deadlock occurred at the end of a template import, when the importer was recomputing statistics for the template's translations. The UI user was editing one of these translations at the time. The deadlock and timeouts were all reported with the same timestamp, which was apparently the moment the database detected and broke the deadlock.
Deadlock traceback: https:/
Recomputing the statistics for all of a template's translations does not take much time, but it covers a lot of data. We can reduce the risk by moving this work into a separate transaction, or even one transaction per translation.
Changed in rosetta: | |
status: | In Progress → Fix Committed |
Changed in rosetta: | |
status: | Fix Committed → Fix Released |
FWIW, it might be interested to track if this behaviour is also the cause of occassional PO file stats skew in our update-stats cronjob.