[wp-trac] [WordPress Trac] #19700: Cron locking still not fixed in 3.3
WordPress Trac
wp-trac at lists.automattic.com
Fri Dec 30 23:56:58 UTC 2011
#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 | Resolution:
Keywords: |
--------------------------+------------------------------
Comment (by archon810):
Finer than a second resolution is definitely needed. Another option would
be to look into mutexes using something like flock or semaphores
(http://stackoverflow.com/questions/2921469/php-mutual-exclusion-mutex),
but really, what I found working great before is microsecond time stored
in a database, then doing an update on that time with a WHERE clause that
takes the microsecond value from the SELECT and seeing how many rows are
updated. If 1, then WHERE matched and you were the first one to grab the
row. If 0, some other process already updated, and you shouldn't do
anything. I'm sure the WP team can figure out the best solution.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/19700#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list