DAG code unpickling issue can crash scheduler #47722
Unanswered
karenbraganz
asked this question in
General
Replies: 1 comment 2 replies
-
This is already handled in Airlfow 3 - we are going to remove pickling option for executor_config. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Apache Airflow version
2.10.5
If "Other Airflow 2 version" selected, which one?
No response
What happened?
I encountered an issue where the code in a single DAG crashed the scheduler resulting in an outage for the entire Airflow instance.
This happened because a user mistakenly included a function object as a value in the
executor_config
dictionary. Certain versions of the dill package are not able to unpickle function objects. When the DAG containing this code started running, the below exception was raised in the scheduling loop and the scheduler pod started CrashLooping.The issue continued until the DAG causing this error was identified and removed.
What you think should happen instead?
We should have safeguards to ensure that DAG code cannot crash the scheduler and cause an outage for the entire Airflow instance. In this case, several other DAGs were not able to run due to the CrashLooping scheduler.
How to reproduce
Operating System
Debian GNU/Linux 12 (bookworm)
Versions of Apache Airflow Providers
No response
Deployment
Astronomer
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions