nathadfield commented on issue #45052:
URL: https://github.com/apache/airflow/issues/45052#issuecomment-2569409115
@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 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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
