Received SIGTERM. Terminating subprocesses. #45379
Replies: 2 comments
-
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
Beta Was this translation helpful? Give feedback.
-
@serhiikovalenkoextcheckrcom Unfortunately I think it's going to be almost impossible for anyone to give you any specific answers to the problem you are facing (which is almost certainly a code or configuration issue on your side) but the possible causes of a SIGTERM in this context could be one of the following. Scheduler Timeout
Manual Termination
Orphaned Process
Resource Constraints
Upstream Dependency or DAG Conflict
|
Beta Was this translation helpful? Give feedback.
-
Apache Airflow version
Other Airflow 2 version (please specify below)
If "Other Airflow 2 version" selected, which one?
2.9.1
What happened?
Sometimes some dags are failing with:
Then task restarts with
What you think should happen instead?
DAG run is successful
How to reproduce
Create a couple of thousands DAGs. It's not a performance issue, CPU and workers are okay.
Operating System
linux (ec2, docker)
Versions of Apache Airflow Providers
No response
Deployment
Docker-Compose
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