title: Locked delayed_job row lingers in the database after capistrano deploy
body: <p>Whenever I deploy with capistrano or run <code>cap production delayed_job:restart</code>, I end up with the currently-running delayed_job row remaining locked.</p>
  
  <p>The delayed_job process is successfully stopped, a new delayed_job process is started, and a new row is locked by the new process. The problem is that the last process' row is still sitting there &amp; marked as locked. So I have to go into the database manually, delete the row, and then manually add that job back into the queue for the new delayed_job process to get to.</p>
  
  <p>Is there a way for the database cleanup &amp; re-queue of the previous job to happen automatically?</p>