1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
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
Conteúdo relevante
- AWS OFICIALAtualizada há 3 meses
- AWS OFICIALAtualizada há 2 anos