poimport (export)_uses a single long transaction, gets reaped

[Michael Vogt]

when trying to get a export of the ddtp-ubuntu-universe component I got the following mail:

"""
Hello Michael Vogt,

Launchpad encountered problems exporting the files you requested.
The Launchpad Translations team has been notified of this problem.
Please reply to this email for further assistance.

If you want to retry your request, you can do so at

https://translations.launchpad.net/ddtp-ubuntu/ubuntu/+pots/ddtp-ubuntu-universe/+export.
"""

This blocks a updated of the apt-ddtp translations for lucid.

Thanks,
 Michael

[Данило Шеган (danilo)]

It seems admins killed the run.

Btw, Michael, is there any reason why you are not making use of the bzr export which should be working well now?

[Данило Шеган (danilo)]

Ok, this happens because transaction killer kills all transaction that are older than 4h. Since poimport is a read-only operation on the DB, adding several transaction.commits() (after each potemplate export, eg.) should solve the problem.

[Stuart Bishop (stub)]

If it is read-only, it should probably be running in autocommit mode.

For performance wins, pull the translations from the slave database while you are there.

[Robert Collins (lifeless)]

This probably oopses now, with the combined work we've done, so raising to critical (though we don't have an actual oops to line up against today)

[Steve Kowalik (stevenk)]

cronscripts/rosetta-export-queue.py is making use of the slave database policy and hasn't been getting reaped recently.