Stores queue consumes too much CPU and memory
Need to work out why, and if using a celery task/queue is really the right thing to do...
Comments (15)
-
-
reporter I don't know. I don't think it is that. It might just be that running a long task like that is inappropriate for Celery. Maybe I should just run it without Celery, with a loop to check if we've asked it not to run anymore, and Celery Beat to start and restart it if it stops.
-
reporter StoreSCP from web interface no longer starts a celery task. Starts and stops successfully from the web interface. TODO: command line start and rethink logging. Refs
#328→ <<cset 42f4742b33c0>>
-
reporter Added basic logging configuration, with override of key values in the example local_settings.py. Only applies to web_store function so far. Refs
#328→ <<cset ecb74cf3b743>>
-
reporter Changed all of storescp to use the new log. Seems to work. Refs
#328→ <<cset af1368c941af>>
-
reporter Changed all of qrscu to use the new log. Seems to work, and continues to log to the celery log too, but for some reason that is at DEBUG level. Refs
#328→ <<cset 0c0e30119246>>
-
reporter Now logs qrscu to separate file. Still logs to celery logs too, but currently only WARNING message that the worker is ready. Refs
#328→ <<cset 2bddaff1aa78>>
-
reporter StoreSCP now has its own log. Refs
#328→ <<cset 05f786d188a2>>
-
reporter Added basic instructions for the new log settings in the install docs. Refs
#328→ <<cset 0bb39f6bc243>>
-
reporter Added upgrade instructions for log config. Refs
#328→ <<cset 2b0edfc31e46>>
-
reporter Merging issue ref
#328back into develop with a view to building a beta for more testing.→ <<cset ec85f3f0b304>>
-
reporter Removed store task. Refs
#328→ <<cset 18d887f24e69>>
-
reporter Hopefully simplified docs relating to starting Celery. Refs
#328as it removes the store queue.→ <<cset bd8aa8ed76c7>>
-
reporter - changed status to resolved
Store SCP no longer uses Celery, so this task should be closed. Ref
#337takes on the new problems that have arisen as a consequence! -
reporter Adding refs
#338,#328to changes→ <<cset b32a5a2a4f0a>>
- Log in to comment
Hmmm. Similar to this? http://stackoverflow.com/questions/19925264/django-1-6-and-celery-3-0-memory-leaks