I don't want worker without timeout. I just want scheduler task not to be
stopped because of timeout from one of thousands records. Why scheduler
doesn't execute tasks with status=='TIMEOUT'?
I have some function like:
thing = db.executesql(db(db.things.id>0)._select(...,
orderby=db.things.up_date))[0]
try:
get url, parse, ...
db.executesql(db(db.things.id==thing[0])._update(availability=True,
up_date=request.now))
except:
db.executesql(db(db.things.id==thing[0])._update(availability=False,
up_date=request.now))
And one wrong URL or 404 break all update system because of timeout, which
stops all task.
среда, 13 ноября 2013 г., 1:48:44 UTC+6 пользователь Niphlod написал:
>
> with no timeout, your worker will try to fetch the site, and if your task
> never returns, it won't process any new task and will remain stuck.
>
> How is it better to have a worker blocked because there is no timeout ?
>
> tl;dr : you won't find any serious task processor without a timeout,
> because it's a really bad design decision.
>
>
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
