You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Daniel Imberman (Jira)" <ji...@apache.org> on 2020/03/27 23:46:00 UTC

[jira] [Commented] (AIRFLOW-305) Fix /dag_stats not to double count TI belonging to the last DAG and still running

    [ https://issues.apache.org/jira/browse/AIRFLOW-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069131#comment-17069131 ] 

Daniel Imberman commented on AIRFLOW-305:
-----------------------------------------

[~sekikn] is this still an issue?

> Fix /dag_stats not to double count TI belonging to the last DAG and still running
> ---------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-305
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-305
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: webserver
>            Reporter: Kengo Seki
>            Assignee: Kengo Seki
>            Priority: Major
>
> Follow-up to AIRFLOW-246. That improved /dag_stats endpoint performance, but it happened to change the result slightly; it double counts the TI belonging to the last DAG run if it is still running. That should be fixed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)