You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/06/20 07:45:34 UTC

[GitHub] [airflow] astolle commented on issue #8722: Kubernetes Pods fail silently when container runs out of memory

astolle commented on issue #8722:
URL: https://github.com/apache/airflow/issues/8722#issuecomment-1160092084

   Hi,
   
   we have the same issue with Airflow v2.2.5, but when using the Kubernetes Executor.
   
   When a POD get's killed by K8S because of OOM, Airflow logs "FAILED" in the scheduler log and nothing to the DAG logs. 
   
   ```
   2022-06-17 06:22:38,609 kubernetes_executor.py INFO - Event: mypod.73f04e8e8d8142c084e0584a9ec7f9dc had an event of type MODIFIED
   2022-06-17 06:22:38,611 kubernetes_executor.py ERROR - Event: mypod.73f04e8e8d8142c084e0584a9ec7f9dc Failed
   ```
   
   Wished behaviour: DAG developers get the reason "why" the DAG (executor pod) failed. 
   
   Best, Alex


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org