Georgy Kibardin ff04eb8394 Moving task cache update into task creation transaction ... Doing this we avoid inclusion of task cache update statement into the next transaction which may cause different problems such as deadlock. In this particular case we've got the following deadlock: 1. DeleteIBPImagesTask makes UPDATE tasks SET cache.... 2. Response handler in receiver makes SELECT clusters FOR UPDATE 3. The code following DeleteIBPImagesTask makes SELECT clusters FOR UPDATE 4. Response handler performs SELECTS tasks FOR UPDATE Change-Id: Ic8e5f2386364421b0667f920499e031f587f726e Closes-Bug: #1653083		2017-01-31 12:31:59 +00:00
..
__init__.py	Files with no code must be left completely empty	2016-09-30 16:13:45 +07:00
fake.py	Enable using new transaction manager for old handlers	2016-09-16 12:51:29 +00:00
helpers.py	Fix cluster progress calculation if Astute didn't send it	2016-10-20 08:03:14 +00:00
legacy_tasks_adapter.py	Change predicate to detect legacy stages for role-based emulation	2016-12-13 20:04:43 +03:00
manager.py	Message format on node(-s) deletion error changed	2017-01-26 20:41:56 +03:00
task.py	Moving task cache update into task creation transaction	2017-01-31 12:31:59 +00:00