Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
cron system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
9 Mar 2012 at 10:38 UTC
Updated:
14 Apr 2012 at 17:12 UTC
Jump to comment: Most recent
Comments
Comment #1
kristiaanvandeneyndeComment #2
marcingy commentedOnly if the batch started more than 864000 seconds ago so approx 10 days. Moving to support request as issue is more than likely in your code
Comment #3
kristiaanvandeneyndeI've tried to reproduce the problem and I came to the conclusion that, if you start your cron at the (almost) exact same time of the batch page doing an ajax POST, you may run into this issue.
Doesn't the query lock the table and thus prevent Batch API from using it, regardless of the condition being met?
Until it is clear that this is not the case, I'd like to keep it under bug report.
Comment #4
marcingy commentedPlease read my comment it deletes entries more than 10 days old therefore if both start at the same time nothing will be deleted. Back to support request.
Comment #5
kristiaanvandeneyndeThe question isn't: does it delete something.
The question is: does it lock the table when it searches for something to delete?
As far as I can tell from the symptoms, it does.
Comment #6
kristiaanvandeneyndeBack to bug report until it's sure this isn't a locking issue
Comment #7
Fixdit commentedWe too are finding a pattern between the cron running and the interruption of our batch API processes.