.. some years ago while running mod_python and Python 2.4, we were
having problems with GracefulShutdownTimeout - some kind of race
condition where the python interpreter would occasionally get wedged
(I don't remember details, something about an atexit handler, the GIL,
and some other nonsense?) The only solution for us at the time was to
stop using GracefulShutdownTimeout and thus shut the children down
hard, which makes our software upgrades a little clunky because we
kill outstanding requests. (the details are long and sordid as to why
we didn't just kill the wedged processes....) I also remember that the
same problem existed with mod_wsgi in embedded mode because of some
fundamental issue embedding the python interpreter in an apache process.
I'm curious if anyone has had this problem before, and if daemon
mode's fundamental architecture is one that would avoid this issue? We
were seeing this really rarely (like every 5 or 10 apache restarts, a
single child would get wedged) so it's hard to really know if it's
fixed until we go into production and let the children sit around a
while.
We're now using daemon mode, and we'd like to turn
GracefulShutdownTimeout, hoping this will work. But it's really hard
to really see if this will be fixed until we try it in a production
environment, which is never good. I'm hoping to get some kind of
answer like "Yes, daemon mode avoids this entirely" or "No, you'll
have the same issue with daemon mode" or even "This is different in
Python 2.6 and higher because the GIL has been changed...."
Alec
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
