跳至内容

how to avoid the SIGKILL signal?

0

Despite the optimized DAG and chunk loading, sometimes tasks are killed automatically, turning into SIGKILL status. Googling this error, most often you can see that it occurs from lack of memory (although, I still delete variables and clear memory during script execution. Question: how to avoid the SIGKILL signal? How to understand whether it is necessary to increase the Environment Airflow MWAA or not, And if increased, by how much?

AWS
已提问 2 年前1067 查看次数
1 回答
0
已接受的回答

Hi, I agree: SIGKILL with Airflow often results from insufficient resources (compute, memory, etc.).

To understand how much your DAG consumes, you can use the CLoudWatch metrics provided by MWAA: see section "Apache Airflow metrics available in CloudWatch" in https://docs.aws.amazon.com/mwaa/latest/userguide/access-metrics-cw-202.html

You will then understand where you consume most and be able to adapt your setup accordingly to avoid the SIGKILLs

Best,

Didier

专家
已回答 2 年前
专家
已审核 2 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。