GitHub user nathadfield edited a comment on the discussion: Received SIGTERM.
Terminating subprocesses.
@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**
* 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.
GitHub link:
https://github.com/apache/airflow/discussions/45379#discussioncomment-11726823
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
