[
https://issues.apache.org/jira/browse/FLINK-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871934#comment-15871934
]
ASF GitHub Bot commented on FLINK-5090:
---------------------------------------
GitHub user NicoK opened a pull request:
https://github.com/apache/flink/pull/3348
[FLINK-5090] [network] Add metrics for details about inbound/outbound
network queues
These metrics are optimised go go through the channels only once in order to
gather all metrics, i.e. min, max, avg and sum. Whenever a request to either
of those is made, all metrics are refreshed and cached. Requests to the
other
metrics will be served from the cache. However, each value will be served
only
once from the cache and a second call to retrieve the minimum, for example,
will refresh the cache for all values.
This setup may at first be a bit strange but ensures that the statistics
belong
together logically and originate from a common point in time. This is not
necessarily the point in time the metric was requested though.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NicoK/flink flink-5090
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3348.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3348
----
commit 59e64c4187c8533e0d802bf415e289624db99f06
Author: Stephan Ewen <se...@apache.org>
Date: 2016-11-17T18:36:56Z
[FLINK-5090] [network] Add metrics for details about inbound/outbound
network queues
These metrics are optimised go go through the channels only once in order to
gather all metrics, i.e. min, max, avg and sum. Whenever a request to either
of those is made, all metrics are refreshed and cached. Requests to the
other
metrics will be served from the cache. However, each value will be served
only
once from the cache and a second call to retrieve the minimum, for example,
will refresh the cache for all values.
This setup may at first be a bit strange but ensures that the statistics
belong
together logically and originate from a common point in time. This is not
necessarily the point in time the metric was requested though.
----
> Expose optionally detailed metrics about network queue lengths
> --------------------------------------------------------------
>
> Key: FLINK-5090
> URL: https://issues.apache.org/jira/browse/FLINK-5090
> Project: Flink
> Issue Type: New Feature
> Components: Network
> Affects Versions: 1.1.3
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
>
> For debugging purposes, it is important to have access to more detailed
> metrics about the length of network input and output queues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
