ashb commented on issue #11899: URL: https://github.com/apache/airflow/issues/11899#issuecomment-718621333
So transaction (1) from the innodb status is this one: https://github.com/apache/airflow/blob/79d71cc5873527eef3661ff1dad134bf0ec4f385/airflow/models/dag.py#L2160-L2180 Transaction (2) is harder to track down exactly, but since it's from the dag parsing process, it'll be https://github.com/apache/airflow/blob/79d71cc5873527eef3661ff1dad134bf0ec4f385/airflow/models/dag.py#L2160-L2180 Which was selected with a lock earlier on in the same function https://github.com/apache/airflow/blob/79d71cc5873527eef3661ff1dad134bf0ec4f385/airflow/models/dag.py#L1767-L1772 Can I just re-iterate again how _wrong_ MariaDB is to call this a _DEAD_ lock. A dead lock is when process A holds locks 1, then tries to get lock 2, and process B holds lock 2 then tries to get lock 1. In the DB status logs _there is only one lock involved_ -- so either the logs aren't useful, or this is just a case of "something else has my lock I should wait/retry". ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
