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 2020/10/09 22:29:29 UTC

[GitHub] [airflow] dennyac edited a comment on issue #9610: Pod logs from KubernetesPodOperator occasionally get replaced with "Task is not able to run"

dennyac edited a comment on issue #9610:
URL: https://github.com/apache/airflow/issues/9610#issuecomment-706425932


   Upvoted that ticket. I understand that this is tied to a celery issue about repeated enqueueing. But there could be valid scenarios where the same job is enqueued more than once. 
   
   I'm concerned how airflow's handling of this scenario as well. Especially about not honoring execution task timeout, determining which job to use to determine task state and logs.
   
   Would be good to have a solution for non Kubernetes deployments as well, as this issue is more generic.


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

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