Closed nikmagini closed 7 years ago
Fix released in 4.2.0
The BlockAllocator agent cycle is now split into two SQL transactions: one to update the t_dpssubs* tables, and another one for the t_dps_block_dest table, so the website can update subs while the agent is working on the dests.
Reported by Jean-Roch: the 'updatesubscriptions' API occasionally takes a long time, up to several minutes, even reaching timeout in the frontends:
Seems to be caused by locks held on the T_DPS_SUBS_DATASET/BLOCK/PARAM tables by the BlockAllocator agent while updating block destinations - consistent with the fact that the agent has a 5-10 minute cycle time nowadays. Looking in session manager, I see that the updatesubscriptions API is locked trying to perform the following update:
While BlockAllocator is busy in the following query: