You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/10/23 21:05:25 UTC

[GitHub] [airflow] potiuk commented on issue #27000: Trigger die with DB deadlock between scheduler

potiuk commented on issue #27000:
URL: https://github.com/apache/airflow/issues/27000#issuecomment-1288201132

   I will re-open this one. It has enough information to try to avoid the deadlock in the first place - the problem is that Triggerer acquires the same locks as scheduler but in a different sequence, the right solution should be to change either Triggerer (most likely) or scheduler (rather unlikely) to apply the same sequence for locks.
   
   Most likely Triggered shoudl attempt to loclk DagRun first and only then update task instance  or even avoid  locking DagRun in the first place.  I believe we fixed a very similar deadlock situation recently.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org