[wp-trac] [WordPress Trac] #57271: Cron unschedule / reschedule event errors

[WordPress Trac]

#57271: Cron unschedule / reschedule event errors
----------------------------------------+------------------------------
 Reporter:  domainsupport               |       Owner:  audrasjb
     Type:  defect (bug)                |      Status:  assigned
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Cron API                    |     Version:  6.0
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+------------------------------

Comment (by domainsupport):

 Replying to [comment:10 chargeup]:
 > Thinking out loud. If the cron job is set on the server for this domain
 http://domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1 then redirects
 to https://www.domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1 could
 that also cause a concurrent request? Just mentioning this as a possible
 cause in those cases for the concurrent request theory.

 Looking at the way the transient is set in `wp-cron.php` with
 `microtime()` it would be almost impossible for the cron to be running
 concurrently as @peterwilsoncc says without the transient being disabled
 (which it isn't on our site). It would require two requests to fire at
 exactly the same microsecond (different hostname request wouldn't matter
 as the transient is stored in the database). The chances of this happening
 would be infinitesimally small and would not present the quantity of
 errors we are seeing.

 It's an absolute mystery!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57271#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform