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/02/24 20:36:37 UTC

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

kaxil commented on issue #9610:
URL: https://github.com/apache/airflow/issues/9610#issuecomment-785358399


   > 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 about how airflow handles this scenario as well. Especially about not honoring task execution 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.
   
   Have you tried it out with Airflow 2.0.1 ? If not can you please test it with it and report back with findings, thanks


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