On Fri, Mar 13, 2015 at 12:49 PM, Tim Tisdall <[email protected]> wrote: > I have setting "harakiri = 60" set. I'm using ugreen so I have > multiple async cores per worker. I'm guessing there's separate timers > per "core", but it seems like it kills the whole worker process. > Maybe it's not practical to just kill a core and context switch out, > or maybe it's trying that and failing, I'm not really sure how it's > working. However, is there any way to tell which core's timer tripped > the harakiri? I suspect it's which ever line has the oldest "since > [timestamp]"?
Hmm.. the oldest "since" in my logs is 1426263768 which is 16:22:48 and the log entry is 16:23:28 so that's only 40 seconds and the harakiri was tripped... I'm kind of confused why it happened now. I just noticed I also have setting "max-requests=1000", so is it possible that it hit the 1000's request and caused a restart via harakiri? Or does it do a more proper restart? (stop taking requests, wait for requests to finish, then restart) _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
