Yeah, makes sense. Well, if you don't want to constantly restart celeryd in
a development setting, you could use this option (auto reload):
http://docs.celeryproject.org/en/latest/whatsnew-2.5.html#experimental-support-for-automatic-module-reloading


On Fri, Feb 7, 2014 at 2:33 PM, Michele Simionato
<notifications@github.com>wrote:

> In openquakeserver/engine/tasks.py:
>
> > @@ -134,10 +109,12 @@ def _trigger_migration(job, callback_url, foreign_calc_id, dbname="platform"):
> >          password=DATABASES[dbname]['PASSWORD'],
> >          port=DATABASES[dbname]['PORT'])
> >
> > -    for output in job.output_set.all():
> > -        copy_output(platform_connection, output, foreign_calc_id)
> > -    update_calculation(callback_url, status="creating layers")
> > -    platform_connection.close()
> > +    try:
> > +        for output in job.output_set.all():
> > +            copy_output(platform_connection, output, foreign_calc_id)
> > +            update_calculation(callback_url, status="creating layers")
>
> Daniele, I have fixed the indentation error.
>
> @Lars <https://github.com/Lars>, ProcessPoolExecutor uses multiprocessing
> which does not play well with Django. Actually > 1 concurrent jobs seems to
> be working for our experiments. In a production setting we will need a
> production-level priority queue, that's for granted. Here I am trying to
> simplify the development setting so that it is easier to develop without
> having to restart servers.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/gem/oq-engine-server/pull/21/files#r9538396>
> .
>