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 [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.
