On Tuesday, January 24, 2017 at 1:59:31 PM UTC-8, Jason Solack wrote: > > Hello all, > > I'm having some re-occurring issue with the scheduler. We are currently > running multiple environments (production, beta) and have several nodes in > each environment. If we have scheduler services running on all machines on > each node we get a lot of deadlock errors. If we drop each environment > down to one node we get no deadlock errors. I am noticing the field > "is_ticker" in the worker table will only have one ticker across all the > workers (spanning environments). Is that the expected behavior? I don't > see any documentation about the ticker field so i'm not sure what to expect > from that. > > Also is there any best practices about running the scheduler in an > environment that i've described? > > Thanks in advance > > Jason >
My scheduler experiences are a lot simpler, so I can't directly answer your questions. But I can ask for more details! Is this a cluster, or independent but related nodes? What db engine is being used for the scheduler tables? Are the deadlocks related to having a lot of work, or happen when the nodes are relatively idle as well? Are tasks recurring or are they in response to client requests? Do tasks not get run because of the problem, or is it just a minor delay? /dps -- 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.
