You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lining (Jira)" <ji...@apache.org> on 2019/11/25 03:08:00 UTC
[jira] [Updated] (FLINK-14815) Expose network metric in
IOMetricsInfo
[ https://issues.apache.org/jira/browse/FLINK-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lining updated FLINK-14815:
---------------------------
Summary: Expose network metric in IOMetricsInfo (was: Expose network pool usage in IOMetricsInfo)
> Expose network metric in IOMetricsInfo
> --------------------------------------
>
> Key: FLINK-14815
> URL: https://issues.apache.org/jira/browse/FLINK-14815
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics, Runtime / Network, Runtime / REST
> Reporter: lining
> Assignee: lining
> Priority: Major
>
> * If sub task is not back pressured, but it is causing a back pressure (full input, empty output)
> * By comparing exclusive/floating buffers usage, whether all channels are back-pressured or only some of them
> {code:java}
> public final class IOMetricsInfo {
> private final float outPoolUsage;
> private final float inputExclusiveBuffersUsage;
> private final float inputFloatingBuffersUsage;
> }
> {code}
> JobDetailsInfo.JobVertexDetailsInfo merge use Math.max.(ps: outPoolUsage is from upstream)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)