You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/03/27 09:54:00 UTC
[jira] [Commented] (AIRFLOW-1421) DAG fails due to timeout: DAG
status from UI unclear
[ https://issues.apache.org/jira/browse/AIRFLOW-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802607#comment-16802607 ]
jack commented on AIRFLOW-1421:
-------------------------------
I'm not sure this is a bug. This is how Airflow works.
Consider a case where you run DAG every 5 minutes.
Run 1 success
Run 2 timeout - failed
Run 3 success
If you look on {color:#333333}Recent Tasks{color} after run 3 you will not see Run 2.
Looking at your schedule interval at the screen shoot it's clear why you think that your idea is a good solution - because your DAG runs once a day so you expect the {color:#333333}Recent Tasks{color} column to reflect it. Your suggestion will not contribute to more frequent dag runs.
The failure is resisted in the {color:#333333}DAG Runs{color} column.
To solve your problem you can set alerts so you will get email notification when DAG failed.
I think this one is a *won't fix*.
> DAG fails due to timeout: DAG status from UI unclear
> ----------------------------------------------------
>
> Key: AIRFLOW-1421
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1421
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
> Affects Versions: 1.8.0
> Reporter: Rebecca Friedman
> Priority: Minor
> Attachments: Screen Shot 2017-07-17 at 12.13.20 PM.png
>
>
> When a DAG fails due to timeout, it's unclear from the DAG list. As you can see in the screenshot, I have hit a case where two of the most recent tasks have run and succeeded. The third task has not been started due to a DAG timeout. Without knowing the total number of tasks in the DAG, it looks like the DAG has succeeded. The only way to tell if the DAG has failed is by clicking on the DAG, and checking the status of the most recent run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)