Did you remember to db.commit() or db.rollback() in your tasks? In the scheduler web2py automatically starts the transaction, but you have to manually COMMIT or ROLLBACK before returning.
On Tuesday, October 23, 2018 at 12:15:35 AM UTC-5, Ruben Quintana wrote: > > I have a lot of errore in the postgres 9.6 log > > < 2018-10-13 17:01:51.039 CST > ERROR: deadlock detected > < 2018-10-13 17:01:51.039 CST > DETAIL: Process 17769 waits for ShareLock > on transaction 32246878; blocked by process 17537. > Process 17537 waits for ExclusiveLock on tuple (0,7) of relation > 16593 of database 16390; blocked by process 17765. > Process 17765 waits for ShareLock on transaction 32246876; blocked > by process 17769. > Process 17769: UPDATE scheduler_worker SET is_ticker='F' WHERE > (scheduler_worker.worker_name <> 'PRTALONENETLAPP-SRV#6852'); > Process 17537: UPDATE scheduler_worker SET is_ticker='F' WHERE > (scheduler_worker.worker_name <> 'PRTALONENETLAPP-SRV#6675'); > Process 17765: UPDATE scheduler_worker SET is_ticker='F' WHERE > (scheduler_worker.worker_name <> 'PRTALONENETLAPP-SRV#6846'); > < 2018-10-13 17:01:51.039 CST > HINT: See server log for query details. > < 2018-10-13 17:01:51.039 CST > CONTEXT: while updating tuple (1,7) in > relation "scheduler_worker" > < 2018-10-13 17:01:51.039 CST > STATEMENT: UPDATE scheduler_worker SET > is_ticker='F' WHERE (scheduler_worker.worker_name <> > 'PRTALONENETLAPP-SRV#6852'); > < 2018-10-13 17:01:52.040 CST > ERROR: deadlock detected > < 2018-10-13 17:01:52.040 CST > DETAIL: Process 17537 waits for ShareLock > on transaction 32246877; blocked by process 17765. > Process 17765 waits for ShareLock on transaction 32246878; blocked > by process 17537. > Process 17537: UPDATE scheduler_worker SET is_ticker='F' WHERE > (scheduler_worker.worker_name <> 'PRTALONENETLAPP-SRV#6675'); > Process 17765: UPDATE scheduler_worker SET is_ticker='F' WHERE > (scheduler_worker.worker_name <> 'PRTALONENETLAPP-SRV#6846'); > < 2018-10-13 17:01:52.040 CST > HINT: See server log for query details. > < 2018-10-13 17:01:52.040 CST > CONTEXT: while updating tuple (0,7) in > relation "scheduler_worker" > < 2018-10-13 17:01:52.040 CST > STATEMENT: UPDATE scheduler_worker SET > is_ticker='F' WHERE (scheduler_worker.worker_name <> > 'PRTALONENETLAPP-SRV#6675'); > > Number of workers:30 > Version 2.14.6-stable+timestamp.2016.05.10.00.21.47 > > from gluon.scheduler import Scheduler > scheduler = Scheduler(db) > > and the use of memory goes up and up and up until it's over (see attached > image). > > -- 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.
