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/12 06:32:00 UTC

[jira] [Updated] (FLINK-14712) Add NetWork metric for IOMetricsInfo

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

lining updated FLINK-14712:
---------------------------
    Description: 
h4. (1) The current monitor is heavy-weight. 
 *   Backpressure monitoring works by repeatedly taking stack trace samples of your running tasks.

h4. (2) It is difficult to find out which vertex is the source  of  backpressure.
 * User need to know current and upstream's network metric to judge current whether is the source of backpressure. Now user has to record relevant information.

h3. Proposed Changes

Update IOMetricsInfo add  outPoolUsage, inputExclusiveBuffersUsage, inputFloatingBuffersUsage:
{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)

According to   !image-2019-11-12-14-30-16-130.png!

  was:
h4. (1) The current monitor is heavy-weight. 
 *   Backpressure monitoring works by repeatedly taking stack trace samples of your running tasks.

h4. (2) It is difficult to find out which vertex is the source  of  backpressure.
 * User need to know current and upstream's network metric to judge current whether is the source of backpressure. Now user has to record relevant information.

h3. Proposed Changes

Update IOMetricsInfo add  outPoolUsage, inputExclusiveBuffersUsage, inputFloatingBuffersUsage:
public final class IOMetricsInfo {    private final float outPoolUsage;    private final float inputExclusiveBuffersUsage;    private final float inputFloatingBuffersUsage;}
 

JobDetailsInfo.JobVertexDetailsInfo merge use Math.max.(ps: outPoolUsage is from upstream)、

According to  !image-2019-11-12-14-30-16-130.png!


> Add NetWork metric for IOMetricsInfo
> ------------------------------------
>
>                 Key: FLINK-14712
>                 URL: https://issues.apache.org/jira/browse/FLINK-14712
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Metrics, Runtime / Network, Runtime / REST
>            Reporter: lining
>            Priority: Major
>         Attachments: image-2019-11-12-14-30-16-130.png
>
>
> h4. (1) The current monitor is heavy-weight. 
>  *   Backpressure monitoring works by repeatedly taking stack trace samples of your running tasks.
> h4. (2) It is difficult to find out which vertex is the source  of  backpressure.
>  * User need to know current and upstream's network metric to judge current whether is the source of backpressure. Now user has to record relevant information.
> h3. Proposed Changes
> Update IOMetricsInfo add  outPoolUsage, inputExclusiveBuffersUsage, inputFloatingBuffersUsage:
> {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)
> According to   !image-2019-11-12-14-30-16-130.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)