airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Whitfield (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRFLOW-1857) Tree View in Web UI does not limit DAGRuns for Dags with execution interval @once or None
Date Tue, 28 Nov 2017 17:29:00 GMT

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

Mark Whitfield updated AIRFLOW-1857:
------------------------------------
    Summary: Tree View in Web UI does not limit DAGRuns for Dags with execution interval @once
or None  (was: Tree View in Web UI shows all DAGRuns for Dags with execution interval @once
or None)

> Tree View in Web UI does not limit DAGRuns for Dags with execution interval @once or
None
> -----------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-1857
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1857
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: ui, webserver
>            Reporter: Mark Whitfield
>            Priority: Minor
>
> The tree view in the web UI relies on the DAG's [execution interval|https://github.com/apache/incubator-airflow/blob/master/airflow/www/views.py#L1178-L1189]
to limit the number of DAG runs displayed. For DAGs with intervals `@once` or `None` this
falls back on the default of displayiing *all* historical runs of the DAG (back to 2000, anyway).
> I have use cases (and believe others do too) involving DAGs which are run exclusively
by manual triggering, whether through the UI, API call, or TriggerDagRunOperator. For long-lived
DAGs of this kind, the UI ends up displaying hundreds of runs, which is not only slow to load
and cumbersome to navigate, but after a while will begin to crash the (containerized, resource-limited)
webserver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message