Hi Guys, I did a thread about a month ago on this topic. I literally chased every solution we could find, rewrote every bit of our code (implemented cursors and batches to eliminate big SQL transfers) and purchase New Relic Silver so we could troubleshoot "background" tasks.
Yet, we still have DJs that just randomly crash. They show NOTHING in the logs. Not even a segfault. They just stop reporting anything. We've implemented a "locked job" view in our admin panel, so at least we know which jobs they are. But, there's no error, no information, nothing in the logs, and nothing to go on. It's getting exceedingly frustrating. What I think and at this point truly believe is this: The DJs that I'm paying for, Heroku's PS monitor simply killing. If this is the case, some suggestion as to what the problem is would be helpful. Is it less memory? CPU? What is the issue? While we can recover, we can't recover if we never get an error message as to what is wrong. Our New Relic shows our overall memory load, and it's less than 200 meg. While that's a lot.. i don't think its bad for 3 front ends and 3 DJs. If anyone has any suggestions, I'm all ears. I'm now "both feet in" having rewritten a large chunk of our code to make it heroku compatible. Only, it seems, to be no further along. Anyone? William -- 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.
