delayed-job

I want to use Delayed::Job (or perhaps a more appropriate job queue to my problem) to dispatch jobs to multiple background daemons. I have several background daemons that carry out different responsibilities. Each one is interested in different jobs in the queue from the Rails app. Is this possible using Delayed::Job, or perhaps there is a different job queue that better fits this task? Since then http://github.com/collectiveidea/delayed_job has reached v3.0 and includes named queues! Excellent for simple grouped queue needs. If you like the Delayed Job, it'd be simple enough to create

Any idea how to get the Delayed::Job id from the ActiveJob enqueuing? When I enqueue a job I get back an instance of ActiveJob::Base with a @job_id , but that job id seems to be internal to ActiveJob. My best guess so far is just to walk down the most recently created jobs: active_job_id = GenerateReportJob.perform_later(self.id).job_id delayed_job = Delayed::Job.order(id: :desc).limit(5).detect do |job| YAML.load(job.handler).job_data['job_id'] == active_job_id end but that seems all kinds of hacky. Kind of surprised ActiveJob isn't returning the ID from Delayed::Job , especially since that

In my Delayed Job, I tried to create a file to tmp folder file_path = Rails.root.join('tmp', "#{file_name}." + file_extension); exported_file = kit.to_pdf # Save file to disk File.open(file_path, 'wb') do |file| file << exported_file end It works well in local but on Heroku there is a error in Delayed Job "No such file or directory - /app/tmp/test.pdf" So how I can solve this problem. I do not want to store file in S3. Thank you Heroku uses what is called an ephemeral filesystem . This means that your local filesystem is only accessible to a single dyno, and once the dyno is stopped, restarted

I'm suffering some weird issue where my delayed_jobs are failing in production. Finally I narrowed it down to the logger. If I comment out my log function calls, everything works. However if I try to log, I get this in the delayed_job handler: --- !ruby/struct:Delayed::PerformableMethod object: AR:User:1 method: :load_and_update_without_send_later args: [] | closed stream /opt/ruby/lib/ruby/1.8/logger.rb:504:in `write' /opt/ruby/lib/ruby/1.8/logger.rb:504:in `write' /opt/ruby/lib/ruby/1.8/monitor.rb:242:in `synchronize' /opt/ruby/lib/ruby/1.8/logger.rb:496:in `write' /opt/ruby/lib/ruby/1.8

How would I silence/ignore these Delayed Job query logs from log/development.log? Delayed::Backend::ActiveRecord::Job Load (1.0ms) UPDATE "delayed_jobs" SET locked_at = '2013-11-19 19:55:45.053991', locked_by = 'host:desktop-virtual pid:22277' WHERE id IN (SELECT id FROM "delayed_jobs" WHERE ((run_at <= '2013-11-19 19:55:45.053435' AND (locked_at IS NULL OR locked_at < '2013-11-19 15:55:45.053519') OR locked_by = 'host:desktop-virtual pid:22277') AND failed_at IS NULL) ORDER BY priority ASC, run_at ASC LIMIT 1 FOR UPDATE) RETURNING * Delayed::Backend::ActiveRecord::Job Load (1.4ms) UPDATE

I've been trying to figure out how to send delayed mail using delayed_job with rails 3. I've tried pretty much every combination of feasible possibilities I can think of - I can get the mail to run in the background, I just can't get it to delay the sending to a future time. The delayed_jobs table in the db clears the tasks, the log says 'sent', the delayed_job task processor picks up the task & says sent without failure...but the mail is either: sent immediately, or simply doesn't arrive if I try to send in the future. If anyone could offer a bare-bones example of a rails 3 delayed_job that