it may look like but that timeline doesn't emit the log according to the scheduler process seeing records (the DEBUG should output "looping..." and/or "sleeping..." at each iteration). Until I see it I can just ask direciton about how to replicate the issue, which I can't do.
On Tuesday, June 7, 2016 at 1:06:14 PM UTC+2, Anthony wrote: > > So i really don't think there can be "several heartbeats before new tasks >> are actually assigned"... >> > > I was just looking at this timeline -- once the task has been queued, > looks like it takes three heartbeats to be assigned: > > 2016-06-02 01:33:00,657 - DEBUG - Adding task to scheduler > 2016-06-02 01:33:00,670 - DEBUG - Done adding task to scheduler > 2016-06-02 01:33:01,060 - DEBUG - scheduler_task: QUEUED > 2016-06-02 01:33:03,253 - DEBUG - scheduler_task: QUEUED > 2016-06-02 01:33:05,198 - DEBUG - scheduler_task: QUEUED > 2016-06-02 01:33:07,196 - DEBUG - scheduler_task: ASSIGNED > 2016-06-02 01:33:09,280 - DEBUG - new task report: COMPLETED > > Anthony > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
