Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Sat, 21 May 2016 16:22:13 +0000 (UTC)
From: "Tyrone Hinderson (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12970211.1463445342000.258994.1463847733879@Atlassian.JIRA>
In-Reply-To: <JIRA.12970211.1463445342000@Atlassian.JIRA>
References: <JIRA.12970211.1463445342000@Atlassian.JIRA> <JIRA.12970211.1463445342107@arcas>
Subject: [jira] [Assigned] (AIRFLOW-123) Differentiate Between Failure and
 Timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 21 May 2016 16:22:18 -0000


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

Tyrone Hinderson reassigned AIRFLOW-123:
----------------------------------------

    Assignee: Tyrone Hinderson  (was: Siddharth Anand)

> Differentiate Between Failure and Timeout
> -----------------------------------------
>
>                 Key: AIRFLOW-123
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-123
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: db, operators, ui
>            Reporter: Kevin Mandich
>            Assignee: Tyrone Hinderson
>            Priority: Minor
>
> Currently, timeouts (when a task's runtime reaches the task-defined timeout) are classified as a failure. It would be useful to differentiate states between a failure due to a timeout and, as an example, a failure due to an exception being raised in a PythonOperator.
> At a minimum, it would be useful to see a task which failed due to timeout visualized as a different color in the Tree View. It would also be nice to utilize this classification as part of DAG logic. Examples here include an option to retry on timeouts specifically, and the ability to take a different action downstream if a particular task failed due to timeout.


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