airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Anand (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRFLOW-138) Airflow improperly shows task status as 'up for retry' for a task that failed on re-run
Date Fri, 20 May 2016 05:01:12 GMT

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

Siddharth Anand updated AIRFLOW-138:
------------------------------------
    Description: 
Migrated from https://github.com/apache/incubator-airflow/issues/1441

Dear Airflow Maintainers,

*Environment*
Before I tell you about my issue, let me describe my Airflow environment:

{panel}
    Airflow version: 1.7.0
    Airflow components: webserver, mysql, scheduler with celery executor
    Python Version: 2.7.6
    Operating System: Linux Ubuntu 3.19.0-26-generic
{panel}

*Description of Issue*
Now that you know a little about me, let me tell you about the issue I am having:

*What I expect:*
If I do a re-run and it fails - The task should be either re-tried again (resetting retry
count) and marked accordingly in GUI OR not retried - and marked in GUI as 'failed'

    What happened instead? The task in the GUI was presented as 'up_for_retry' however it
was not retried, even after retry_delay has passed

*Reproducing the Issue*

DAG does not have some strange settings:
{code}
concurrency= 3,
max_active_runs = 2,
start_date = datetime(2016,04,03,01),
default_args={
'depends_on_past': False,
'retries': 2,
'retry_delay': timedelta(minutes=3) }
{code}


  was:
Migrated from https://github.com/apache/incubator-airflow/issues/1441

Dear Airflow Maintainers,
Environment

Before I tell you about my issue, let me describe my Airflow environment:

    Airflow version: 1.7.0
    Airflow components: webserver, mysql, scheduler with celery executor
    Python Version: 2.7.6
    Operating System: Linux Ubuntu 3.19.0-26-generic

Description of Issue

Now that you know a little about me, let me tell you about the issue I am having:

What I expect:
If I do a re-run and it fails - The task should be either re-tried again (resetting retry
count) and marked accordingly in GUI OR not retried - and marked in GUI as 'failed'

    What happened instead? The task in the GUI was presented as 'up_for_retry' however it
was not retried, even after retry_delay has passed

Reproducing the Issue

DAG does not have some strange settings:
concurrency= 3,
max_active_runs = 2,
start_date = datetime(2016,04,03,01),
default_args={
'depends_on_past': False,
'retries': 2,
'retry_delay': timedelta(minutes=3) }



> Airflow improperly shows task status as 'up for retry' for a task that failed on re-run
> ---------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-138
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-138
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: Airflow 1.7.0
>            Reporter: Tomasz Bartczak
>            Assignee: Siddharth Anand
>            Priority: Minor
>
> Migrated from https://github.com/apache/incubator-airflow/issues/1441
> Dear Airflow Maintainers,
> *Environment*
> Before I tell you about my issue, let me describe my Airflow environment:
> {panel}
>     Airflow version: 1.7.0
>     Airflow components: webserver, mysql, scheduler with celery executor
>     Python Version: 2.7.6
>     Operating System: Linux Ubuntu 3.19.0-26-generic
> {panel}
> *Description of Issue*
> Now that you know a little about me, let me tell you about the issue I am having:
> *What I expect:*
> If I do a re-run and it fails - The task should be either re-tried again (resetting retry
count) and marked accordingly in GUI OR not retried - and marked in GUI as 'failed'
>     What happened instead? The task in the GUI was presented as 'up_for_retry' however
it was not retried, even after retry_delay has passed
> *Reproducing the Issue*
> DAG does not have some strange settings:
> {code}
> concurrency= 3,
> max_active_runs = 2,
> start_date = datetime(2016,04,03,01),
> default_args={
> 'depends_on_past': False,
> 'retries': 2,
> 'retry_delay': timedelta(minutes=3) }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message