Hi!
I have developed a web application using web2py with the aim of
configuring little single boards so I thought to use the web interface
to set up variables and configuration files and the scheduler, that run
with root privileges, to apply configurations.
The problem is that to have near real time performances I set up a
really hight heartbeat (0.3 seconds) and each time the user apply the
configuration a task is queued with immediate parameter set to True.
Now sometime happens that the scheduler worker stops to make their job
and does not take charge of tasks no more.
Trying to understand what happend I found that the worker in their
worker_stats is still configured as "running" even if ended up the last
task with success.
The only way to come out from theese kind of situations is to restart
the scheduler daemon or reset the worker removing the record in the db
table and let the scheduler to create a brand new worker record.
Does anybody had similar experiences or have any suggestions?
Any idea how to automatically stress the scheduler in order to
understand their performances limit?
Thank you very mutch
Cheers
Manuele
--
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.
