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/27 10:40:00 UTC

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

     [ https://issues.apache.org/jira/browse/AIRFLOW-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sébastien GENESTA closed AIRFLOW-5872.
--------------------------------------
    Resolution: Abandoned

> 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
>            Priority: Minor
>
> 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)