[wp-trac] [WordPress Trac] #19700: Cron locking still not fixed in 3.3

[WordPress Trac]

#19700: Cron locking still not fixed in 3.3
--------------------------+-----------------------------
 Reporter:  archon810     |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Cron          |    Version:  3.3
 Severity:  major         |   Keywords:
--------------------------+-----------------------------
 Re-opening the issue due to #17462 not fixing the problem once and for
 all.

 This is what I posted as the last comment there before getting instructed
 to start a new ticket:

 > I don't think the bug is fixed. After posting a new post, I experienced
 a load spike (2 -> 20) and found this in the server status:
 http://minus.com/m1VuUQcxP

 Additionally, today I stuck an error_log() statement into something that
 gets scheduled like this:
 {{{
 function my_publish_post($new_status, $old_status, $post) {
   wp_schedule_single_event(time()+150, 'my_feedburner_ping');
 }
 add_action( 'my_feedburner_ping', 'my_feedburner_ping' );
 function my_feedburner_ping() {
 error_log(print_r(wp_remote_get("http://feedburner.google.com/fb/a/pingSubmit?bloglink="
 . urlencode(home_url())), 1));
 }
 }}}

 The log shows 2 events, on the exact same second. [Fri Dec 30 10:02:26
 2011] [error] and so on. The HTTP headers are different, so I know 2
 separate requests went out. And this is on a relatively slow eve of New
 Year's eve and a load of 2 on a quad-core machine. If the server was more
 loaded, we could probably see 5-10 of these.

 The current solution doesn't seem to be truly atomic and multi-thread
 friendly.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/19700>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software