[wp-trac] [WordPress Trac] #11800: doubled execution of cron jobs

[WordPress Trac]

#11800: doubled execution of cron jobs
--------------------------+-------------------------------------------------
 Reporter:  neoxx         |       Owner:  westi         
     Type:  defect (bug)  |      Status:  new           
 Priority:  normal        |   Milestone:  Future Release
Component:  Cron          |     Version:  2.9.1         
 Severity:  normal        |    Keywords:  cron          
--------------------------+-------------------------------------------------
Changes (by westi):

  * milestone:  2.9.2 => Future Release


Comment:

 Replying to [comment:1 miqrogroove]:
 > Idea for a fix: Create a proper token for each future job.  In wp-
 cron.php, consume that token at the top of the script.  Since the token
 can only be used once, any races are broken and the concurrent jobs may
 self-quit.

 This means we can only process on cron task per page load of wp-cron.php.

 For me one of the biggest problems with cron at the moment is that it is
 all stored in a single option.

 This makes it hard to do atomic actions on the data - especially if people
 are using an object cache / running across multiple servers.

 You can't atomically add/remove a cron task at the moment.

 I think it would be best to look into fixing this problem rather than
 papering over the cracks.

 The best solution here is probably to split the cron jobs off so they are
 stored as single job per row in the db.

 Moving out of 2.9.2 as I think this needs a structural fix.
 Moving to Future Release for now as there is no patch and no guarantee it
 will be fixed in the 3.0 dev cycle.

 If someone wants to attempt this I would be happy to review patches and
 discuss ideas.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11800#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software