Steve Howell c0bf3bb191 [deploy] Have most queue works commit on success. ... Deployment instructions: I think all the queue workers get restarted automatically, so there is probably nothing special to do here in the deploy itself, but we will want to monitor it closely, and the change should make our number of locks go down. QueueProcessingWorker.start() now calls consume_and_commit(), which ensures that we don't hold locks after work actions by using Django's commit_on_success() decorator. Obviously, workers that override start() will not call consume_and_commit() through this code path. SlowQueryWorker calls commit_on_success() in its start() method now, and I hope to address MissedMessageWorker soon. (imported from commit f3f38a7f45730eee8f3b5794371ba5b994017676)		2013-10-17 15:36:39 -04:00
..
__init__.py	Add new system for defining and running queue-processing workers	2013-09-24 20:44:15 -04:00
queue_processors.py	[deploy] Have most queue works commit on success.	2013-10-17 15:36:39 -04:00