-
Notifications
You must be signed in to change notification settings - Fork 15.1k
MySQL deadlock when using DAG serialization #8521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
I encountered the same problem. Is this problem solved now? |
Same problem +1 |
Same problem +1 |
Hi, I have the same issue. I was looking in
contains a line that loads the number or rendered fields to keep:
and if this value is <= 0 the function will return doing nothing.
Since the dead lock is about the insert and the delete in that table, setting max_num_rendered_ti_fields_per_task = 0 inside the [core] config ... perhaps can fix the issue. Of course it does not work. Using
-----> Please note LIMIT 30 I found this code inside
and it's the unique place where delete_old_records is called, so ... it is weird, is it not? I'll investigate better tomorrow... |
|
In my case issue is about concurrent dags, the insertion issue is fixed in airflow Steps to reproduce:
If X tasks of a dag ran at the same time, (X - 1) of them will face lock and just 1 of them return success!
|
Is this issue still present in 1.10.12? |
|
I will mark it as fixed then @zorseti. I think we can always re-open in case we still see it happening :) |
@honarkhah May I know how did you fix the concurrent task under subdagoperator issue. I am still facing it. I have raised a similar question here : https://stackoverflow.com/questions/70263466/airflow-1-10-14-subdagoperator-failing-with-deadlock-issue |
Apache Airflow version: 1.10.10
Kubernetes version: v1.16.8
MySQL version: 5.7
What happened:
Airflow tasks fail with Deadlock when running Dag with
max_active_runs
> 1 andconcurrency
> 1 and whendag_serialization
is enabled.Logs
The text was updated successfully, but these errors were encountered: