Hi Dave, This is a problem for you? I've had my scheduler running on AWS and > Postgres for months without issue. I actually have a second scheduler > running in sqlite3 on the same machine. No issue. >
Actually it becomes more of an issue if you are on a shared server with a limited shared resources plan. Some limit number of long running processes as well as RAM. Also there is the extra RAM used (my scheduler process started at 35Mb and slowly crept up over time). Things that aren't python are better run via system cron, but the scheduler > does a fine job for application-related pythonic work. > My main problem was I had a few situations where my main scheduler process would just completely hang on a task (not the same one each time). Never figured out the actual cause (no errors or tickets) but I had to write a script that would periodically (run from cron ;) ) interrogate the scheduler worker tables for last run times and status and warn me if something was out of bounds. Fiddling with worker statuses, etc. in the tables didn't resolve the issue - I had to kill -9 the process and restart it. This is with 2.18.5 on CentOS. When I refactored the code to move to python3 I moved to using crontab and, with my use case, not had a single problem since. Each task runs independently and one 'glitch' does not stop all other tasks from running which caused me some grief. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/47d77c25-4abd-4b94-bd7c-d36a446dd52fo%40googlegroups.com.
