You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Vijay Bhat (JIRA)" <ji...@apache.org> on 2016/12/05 21:25:58 UTC

[jira] [Updated] (AIRFLOW-673) Add operational metrics test for SchedulerJob

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

Vijay Bhat updated AIRFLOW-673:
-------------------------------
    Summary: Add operational metrics test for SchedulerJob  (was: Operational metrics test for SchedulerJob)

> Add operational metrics test for SchedulerJob
> ---------------------------------------------
>
>                 Key: AIRFLOW-673
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-673
>             Project: Apache Airflow
>          Issue Type: Test
>          Components: core, scheduler, tests
>            Reporter: Vijay Bhat
>            Assignee: Vijay Bhat
>
> Add a performance test to supply operational metrics for SchedulerJob. We want to know if any DAG is starved of resources, and this will be reflected in the stats printed out at the end of the test run.
> Please refer to the discussion in the PR - https://github.com/apache/incubator-airflow/pull/1906.
> @bolkedbruin - This has operational consequences which I can not fully oversee. Such as the scheduling now might be biased towards one dag (ie. do other dags run at all?). While this issue is already there it might become more prevalent because of this.
> Can you supply operational metrics @vijaysbhat?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)