Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Came up with a solution that works.</p> <p>I have a base class that all of my delayed jobs inherit from called <code>BaseJob</code>:</p> <pre><code>class BaseJob attr_accessor :live_hash def before(job) # check to make sure that the version of code here is the right version of code resp = HTTParty.get("#{Rails.application.config.root_url}/revision") self.live_hash = resp.body.strip end def should_perform() return self.live_hash == GIT_REVISION end def perform() if self.should_perform == true self.safe_perform() end end def safe_perform() # override this method in subclasses end def success(job) if self.should_perform == false # log stats here about a failure # enqueue a new job of the same kind new_job = DelayedJob.new new_job.priority = job.priority new_job.handler = job.handler new_job.queue = job.queue new_job.run_at = job.run_at new_job.save job.delete # restart the delayed job system %x("export RAILS_ENV=#{Rails.env} &amp;&amp; ./script/delayed_job stop") else # log stats here about a success end end end </code></pre> <p>All base classes inherit from <code>BaseJob</code> and override <code>safe_perform</code> to actually do their work. A few assumptions about the above code:</p> <ul> <li><code>Rails.application.config.root_url</code> points to the root of your app (ie: www.myapp.com)</li> <li>There is a route exposed called <code>/revision</code> (ie: www.myapp.com/revision)</li> <li>There is a global constant called <code>GIT_REVISION</code> that your app knows about</li> </ul> <p>What I ended up doing was putting the output of <code>git rev-parse HEAD</code> in a file and pushing that with the code. That gets loaded in upon startup so it's available in the web version as well as in the delayed_job consumers. </p> <p>When we deploy code via Capistrano, we no longer stop, start, or restart delayed_job consumers. We install a cronjob on consumer nodes that runs every minute and determines if a delayed_job process is running. If one isn't, then a new one will be spawned.</p> <p>As a result of all of this, all of the following conditions are met:</p> <ul> <li>Pushing code doesn't wait on delayed_job to restart/force kill anymore. Existing jobs that are running are left alone when new code is pushed.</li> <li>We can detect when a job begins if the consumer is running old code. The job gets requeued and the consumer kills itself.</li> <li>When a delayed_job dies, a new one is spawned via a cronjob with new code (by the nature of starting delayed_job, it has new code).</li> <li>If you're paranoid about killing delayed_job consumers, install a nagios check that does the same thing as the cron job but alerts you when a delayed_job process hasn't been running for 5 minutes.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow to gracefully restart delayed_job consumers?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USfffanatics
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to gracefully restart delayed_job consumers?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload