[wp-trac] [WordPress Trac] #57924: Cron Goes Missing. _set_cron_array called with incorrect number of crons

[WordPress Trac]

#57924: Cron Goes Missing. _set_cron_array called with incorrect number of crons
--------------------------+------------------------------
 Reporter:  j3gaming      |       Owner:  j3gaming
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Cron API      |     Version:  6.1.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by j3gaming):

 @SergeyBiryukov Could be related, but each ticket has different outcomes.
 My ticket is to resolve crons being deleted. The other ticket is a spammed
 error log that is connected to some db updates that previously had silent
 failures.

 @galbaras I'm able to reproduce it by running my database backup. The
 backup take 3-5 minutes to complete, and causes my site to be in an
 intermittent state. Looks of dropped connections, and what users would
 describe as "lag". While running my backup, it is very comparable to what
 a DDOS would look like.

 @tobifjellner I think that's incredibly close, or exactly what's
 happening.

 @domainsupport Yes, my cron fires each minute. Even when I set it to fire
 every 10 minutes, I can still reproduce the issue, as long as that backup
 is running while a cron is set to run. Because I'm able to reproduce the
 issue by simply doing a backup, while a cron is set to run, the recurrence
 timing of the cron is not related in my opinion.

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