ActiveRecord batches won't work for you? http://rdoc.info/docs/rails/2.3.8/ActiveRecord/Batches/ClassMethods
Both methods default to 1000 results per batch, but can be configured with the :batch_size option. Mike On Mon, Oct 4, 2010 at 10:56 AM, William Flanagan <[email protected]> wrote: > Nope, we love empty queues. > I think it comes down to memory, that we aren't cursoring the output from > the database. We are rewriting our code to implement our own cursor support, > since AR doesn't support it. > The hard part is that we get no information from the process when it > crashes. We were finally smart enough to write custom code that tells us > which job rows are locked, so we can start the troubleshooting process that > way, since the lock is not cleared. > > But, the bigger issue is this: I have had this ticket open 5 days and this > is the first bit of communication we have had. We are writing our methods to > support heroku specifically at this point, and for it to take 5 days to get > any response seems like too long. > I have opened 2 tickets in my history with heroku, both took almost 1 week > to get a response. What does someone do if their app is in production and > completely down? Wait a week? Is this typical? If so, I need to know that. > Any thoughts anyone? > > Sent from my iPad > On Oct 4, 2010, at 13:28, Brandon Casci <[email protected]> wrote: > > William...this may sound trivial, but to your DJ workers crash if the work > queues is empty? > > On Mon, Oct 4, 2010 at 1:08 PM, Dan Croak <[email protected]> wrote: >> >> There are some troubleshooting suggestions on this page: >> >> http://docs.heroku.com/ps >> >> On Mon, Oct 4, 2010 at 1:04 PM, Brandon Casci <[email protected]> >> wrote: >> > I can only offer commiseration because I'm in the same position as you >> > ;) >> > >> > Please let me know what they say. >> > >> > What do your jobs do? >> > >> > On Thu, Sep 30, 2010 at 8:58 AM, WilliamF <[email protected]> >> > wrote: >> >> >> >> Hi all, >> >> >> >> I'm looking for suggestions, as I'm not getting a response from >> >> Heroku. >> >> >> >> My background DJ workers are crashing. I can't seem to make them stay >> >> up for more than 15 or so seconds. If I look at the logs, the error >> >> message I'm getting is: >> >> >> >> >> >> RPM Monitoring DJ worker host:railgun64.29642 pid:29790 >> >> *** Starting job worker host:railgun64.29642 pid:29790 >> >> /usr/ruby1.8.7/lib/ruby/1.8/uri/common.rb:385: [BUG] Segmentation >> >> fault >> >> ruby 1.8.7 (2010-04-19 patchlevel 253) [x86_64-linux], MBARI 0x6770, >> >> Ruby Enterprise Edition 2010.02 >> >> >> >> NewRelic doesn't show the DJ worker in its logs that I can >> >> troubleshoot. NewRelic states: RPM recorded no DelayedJob background >> >> task executions in the last 30 minutes. >> >> >> >> Which, needless to say, isn't the most helpful. >> >> >> >> I've taken every job that I can find that is outstanding and locked in >> >> the database, duplicated the data down to my local machine, and run my >> >> machine in production mode. The workers are able to process these just >> >> fine on my local machine. >> >> >> >> Given this, and the lack of response by Heroku, I'm stuck. I'd love >> >> some suggestions as to the best/next way to go to troubleshoot this >> >> problem. Background tasks are CORE to my application. If the >> >> background tasks don't work, my app is dead in the water. >> >> >> >> Help! >> >> >> >> 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. >> >> >> > >> > >> > >> > -- >> > ========================================= >> > Brandon Casci >> > Loudcaster >> > http://loudcaster.com >> > ========================================= >> > >> > -- >> > 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. >> > >> >> -- >> 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. >> > > > > -- > ========================================= > Brandon Casci > Loudcaster > http://loudcaster.com > ========================================= > > -- > 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. > > -- > 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. > -- 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.
