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.
You can confirm this behaviour here by catching and logging the SIGTERM in your app and then reproducing the situation you describe. If you can provide a test-case that shows you're not seeing expected behaviour (I use it extensively in one of my test apps) I'll make a ticket gets filed against the Runtime. Otherwise, maybe there's somewhere we can improve our documentation here. Regards, Peter Heroku On Wed, May 11, 2011 at 8:49 PM, midwaltz <ste...@gmail.com> wrote: > > When decreasing Dynos while they are busy, some of them return a 503 > status error with Heroku error code H13 (Connection closed without > response > http://devcenter.heroku.com/articles/error-codes#h13__connection_closed_without_response > ). > > I can only speculate, but to me it looks like instead of waiting for > the Dyno to finish sending its request, the Dyno is killed right away. > > After a quick Googling I found out this bug might have been known for > a while: > http://www.continuousthinking.com/2010/11/3/heroku-autoscaling-bug > (except the error status codes look different, but it might have been > a misstep?). > > What's the status on fixing this bug? > > Cheers, > Steph > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
