You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/19 12:02:00 UTC

[jira] [Commented] (AIRFLOW-3125) Add monitoring on Task Instance creation rate

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

ASF subversion and git services commented on AIRFLOW-3125:
----------------------------------------------------------

Commit 7c3ab0447b647967835b24c609aeebc6506678e3 in airflow's branch refs/heads/v1-10-test from Mingye Xia
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=7c3ab04 ]

[AIRFLOW-3125] Monitor Task Instances creation rates (#3966)

Montor Task Instances creation rates by Operator type.
These stats can provide some visibility on how much workload Airflow is
getting. They can be used for resource allocation in the long run (i.e.
to determine when we should scale up workers) and debugging in scenarios
like the creation rate of certain type of Task Instances spikes.

> Add monitoring on Task Instance creation rate
> ---------------------------------------------
>
>                 Key: AIRFLOW-3125
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3125
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Mingye Xia
>            Assignee: Mingye Xia
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Monitoring on Task Instance creation rate can give us some visibility on how much workload we are putting on Airflow. It can be used for resource allocation in the long run (i.e. to determine when we should scale up workers) and and debugging in scenarios like creation rate for certain types of Task Instances spike.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)