Scheduler Timeout
- The Airflow scheduler may have enforced a task timeout (e.g., due to exceeding the execution_timeout parameter) and sent SIGTERM to stop the task.
Manual Termination
- A user or system admin may have manually terminated the task using airflow tasks kill or similar commands.
Orphaned Process
- The PID mismatch suggests that the task may have been restarted or orphaned, causing Airflow to send SIGTERM to clean up inconsistent state.
Resource Constraints
- The system or container running Airflow might have terminated the process due to resource exhaustion (e.g., memory, CPU limits).
Upstream Dependency or DAG Conflict
- If the task was part of a larger workflow, another task or operator failure could trigger an early termination.
https://github.com/apache/airflow/issues/45052
Received SIGTERM. Terminating subprocesses. · Issue #45052 · apache/airflow
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: [2024-12-16, 07:33...
github.com
1. Timeout 확인
2. Airflow 서버 리소스 확인 - 그라파나
3. 해당 에러 발생했던 Dag 시간대 및 규칙 확인
반응형
'Echo system > Airflow' 카테고리의 다른 글
Airflow configuration (0) | 2025.04.20 |
---|---|
dag parsing & write_dag (0) | 2025.04.18 |
Airflow - Custom provider 생성 (1) | 2024.10.09 |
Airflow - Custom 패키지 만들기 (0) | 2024.09.23 |
Airflow - Custom hook, operator, sensor 생성하기 (1) | 2024.09.23 |