flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4923) Expose input/output buffers and bufferPool usage as a metric for a Task
Date Wed, 02 Nov 2016 09:49:58 GMT

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

ASF GitHub Bot commented on FLINK-4923:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/flink/pull/2727


> Expose input/output buffers and bufferPool usage as a metric for a Task
> -----------------------------------------------------------------------
>
>                 Key: FLINK-4923
>                 URL: https://issues.apache.org/jira/browse/FLINK-4923
>             Project: Flink
>          Issue Type: Improvement
>          Components: Metrics
>            Reporter: zhuhaifeng
>            Assignee: zhuhaifeng
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> We should expose the following Metrics on the TaskIOMetricGroup:
>  1. Buffers.inputQueueLength: received buffers of InputGates for a task
>  2. Buffers.outputQueueLength: buffers of produced ResultPartitions for a task
>  3. Buffers.inPoolUsage: usage of InputGates buffer pool for a task
>  4. Buffers.outPoolUsage: usage of produced ResultPartitions buffer pool for a task



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

Mime
View raw message