Thank you for the tip about changing the status to PICK. Ill use that next time if this ever occurs again.
On Wednesday, November 11, 2015 at 5:25:30 AM UTC-5, Niphlod wrote: > > this is handled automatically by each and every worker every 5 cycles > (with default heartbeat of 3 seconds, it's 15 seconds). > You can "force" the job that is done every 5 cycles setting "PICK" as a > status on the workers. > > That being said, if it doesn't add up in your environment you'd better > triplecheck if there are exceptions going around: what you're experiencing > should last 15 seconds AT THE MOST. > > On Tuesday, November 10, 2015 at 9:33:38 PM UTC+1, Benson Myrtil wrote: >> >> I am running on a windows server 2008. I have nssm setup which manages my >> 4 worker nodes. The workers appear to be working correctly in the sense >> that the heartbeat is consistently updating. However, the tasks are stuck >> in the QUEUE status assigned to old worker nodes that do not exist. >> >> Is there a way to force the scheduler to update the assignments every so >> often or at least to check to make sure they are assigned to 'living' >> workers? >> > -- 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.
