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

Posted to commits@airflow.apache.org by "Sébastien GENESTA (Jira)" <ji...@apache.org> on 2019/11/08 09:00:02 UTC

[jira] [Created] (AIRFLOW-5872) task up_to_retry without starting (queue then up_to_retry)

Sébastien GENESTA created AIRFLOW-5872:
------------------------------------------

             Summary: task up_to_retry without starting (queue then up_to_retry)
                 Key: AIRFLOW-5872
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5872
             Project: Apache Airflow
          Issue Type: Bug
          Components: DAG, DagRun, scheduler
    Affects Versions: 1.10.0
            Reporter: Sébastien GENESTA


Hi,

We are encountering issue with tasks that fall in "up_to_retry" state just after being queued, then start and success few minutes later.

Logs in the "up_to_retry" tasks are empty and operator display "null".

We don't have any clue of what happen.

Any suggestions, ideas to help us to investigate?

Thanks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)