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 2021/11/08 20:07:56 UTC

[GitHub] [airflow] sweco edited a comment on issue #19329: Kubernetes Executor: non-existent upstream failed

sweco edited a comment on issue #19329:
URL: https://github.com/apache/airflow/issues/19329#issuecomment-963226239


   Hey there, we're observing the same issue on Airflow 2.1.4 in a big DAG having hundreds of tasks. By looking in the scheduler logs from the moment when the downstream task was marked as `upstream_failed` it seems that it happened when a pod with the upstream task could not be started.
   
   ```
   Failed to start pod ...
   ```
   
   Also, looking at the successful task, it indeed has two tries, from which the first one really finished at the incriminated timestamp.
   
   ![image](https://user-images.githubusercontent.com/11132999/140761583-527a3754-a51d-410a-90b0-e596ab0e8c23.png)


-- 
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