airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Mandich (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AIRFLOW-123) Differentiate Between Failure and Timeout
Date Fri, 20 May 2016 22:05:12 GMT

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

Kevin Mandich reassigned AIRFLOW-123:
-------------------------------------

    Assignee: Kevin Mandich  (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: Kevin Mandich
>            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)

Mime
View raw message