I am in the same boat as Tim. Despite very low traffic and two active dynos, my site tends to go down with a permanent "Backlog too deep" and no other resolution than rebooting the app. It is very frustrating to have the app go down like this from time to other, with no logs and no way to debug it.
I have no long running processes in the dynos - everything like that goes to Delayed Job, even sending out emails. Cheers, Casper Fabricius On 27/12/2009, at 19.45, Tim wrote: > There was a thread a few months ago regarding "backlog too deep" that > seems to be closed now: > > http://groups.google.com/group/heroku/search?group=heroku&q=backlog+too+deep++&qt_g=Search+this+group > > I had the same issue this morning. My small Heroku-hosted app went > down showing the "backlog too deep" error. However, checking Google > Analytics and New Relic I can't find anything that would point to > increased traffic (only ~25 visits/day) or a problem with the app > (performance indicators all seem to be within the New Relic default > margins). > > Is there anywhere else I should check? Rebooting the app brought the > site back up, but I'd like to investigate and find out what caused > this, if possible. > > Thanks, > Tim > > -- > > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@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 her...@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.
