> Hello All,
>
> I'm running uwsgi 1.0.2.1 in emperor mode.  Due to threading issues
> related
> to sqlalchemy I'm running my apps in lazy mode.  Since moving to lazy mode
> I've had issues reloading my app.  While the uwsgi log does report the app
> reloading:
>
> [emperor] reload the uwsgi instance app.ini
> Tue Jan 31 22:19:41 2012 - received message 1 from emperor
> ...gracefully killing workers...
> Gracefully killing worker 1 (pid: 15269)...
> Respawned uWSGI worker 1 (new pid: 15351)
> WSGI application 0 (mountpoint='') ready on interpreter 0xea0530 pid:
> 15351
> (default app)
>
> However, uwsgi appears to be running the same app as before the reload
> (I've replaced the .ini file with one that points to a new app).  I've
> tried this without the --lazy option and the app reloads correctly.
>
> Is touch reload broken with the lazy mode?
>

Hi, there is an experimental option

--propagate-touch

that should fix touch-reload in lazy mode.

It is not enabled by default as i did not receive enough test reports.

let me know if it works for you.

-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to