[
https://issues.apache.org/jira/browse/AIRFLOW-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286002#comment-15286002
]
Kevin Mandich commented on AIRFLOW-123:
---------------------------------------
Hi Chris,
I had number 3 in mind. I'll update the description to specify this. I was
thinking it'd be useful to see if a task failed because the runtime reached the
task-defined timeout. You can of course just check the log of the individual
task, but in my use case I sometimes have to take different actions depending
on the failure mode and it would be nice to just take the action at the Tree
View level (e.g. clear from some upstream point without going into the logs).
This leads to my second wish - the ability to automate these actions by
programming them directly into the DAG, and as a function of the failure mode.
> 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
> Priority: Minor
>
> Currently, timeouts are classified as a failure (both task and DAG). 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)
