shivanshs9 commented on issue #11899: URL: https://github.com/apache/airflow/issues/11899#issuecomment-718640942
> 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". Yeah it does seems fishy. From what I'm able to understand from InnoDB output, SELECT Transaction (1) doesn't even hold any lock but waiting for locks held by UPDATE Transaction (2). And Transaction (2) is waiting for some other lock. :shrug: > Could you try with AIRFLOW__CORE__STORE_DAG_CODE=False @shivanshs9 ? If that helps I have an idea. @ashb Nope, still facing the same issue: ``` $ airflow config get-value core store_dag_code False ``` ---------------------------------------------------------------- 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]
