On May 12, 10:15 am, Peter van Hardenberg <[email protected]> wrote: > We normally send a SIGTERM, then wait five (ish?) seconds to let the last > request serve and then, then send SIGKILL if the process still hasn't gone > away.
I'm going to go ahead and ignore the fact that I know nothing about the infrastructure's implementations and their constraints --- but from this side of things it looks like this problems stems from the fact that you rely heavily on the applications and/or thin to gracefully finish a request after receiving a SIGTERM. If I may ask, why don't you first wait for the request to finish, and if it doesn't finish after an interval, *then* send a SIGTERM? -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
