To Nha Notes | May 31, 2023, 8:41 a.m.
The following sections describe symptoms and potential fixes for some common DAG issues.
Sometimes your task might be using more memory than Airflow worker is allocated. In such a situation it might be interrupted by Negsignal.SIGKILL. The system sends this signal to avoid further memory consumption which might impact the execution of other Airflow tasks. In the Airflow worker's log you might see the following log entry:
{local_task_job.py:102} INFO - Task exited with return code Negsignal.SIGKILL
Possible solutions:
Lower worker_concurrency of Airflow worker
In the case of Cloud Composer 2, increase memory of Airflow workers
In the case of Cloud Composer 1, upgrade to bigger machine type used in Composer cluster
Optimize your tasks to use less memory