Hello,
So the configuration might not be ideal, but these small config tweaks
shoun't be really the source of the issue right? It's a bit odd since I
haven't had issues with similar deploys. This project I guess uses more
libraries C extensions (lxml and postgres) and the background threads/pools
perform a lot of IO (email sending, message queue polling, and some
others), although they are all under daemon threads and should finish under
the 4 seconds grace time.
Would setting WSGIApplication Group %{GLOBAL} still allow me to use more
than 1 process on the daemon configuration? Although I don't think it will
do any change at all since the web servers only listen on port 80 and are
on the same domain so all requests should always be falling into the same
application group if I interpreted the docs correctly.
This issue is so random and since only happens on cloud deploys it gets
really difficult to test if a change helped or not and it can take days to
notice it. I guess I will keep playing around with settings and try to
gather more info of the stuck processes when it happens.
Thank you so much for all the help!
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
