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

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

Github user tillrohrmann commented on a diff in the pull request:

    https://github.com/apache/flink/pull/3377#discussion_r102465162
  
    --- Diff: 
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/IOMetrics.java
 ---
    @@ -53,6 +53,22 @@ public IOMetrics(Meter recordsIn, Meter recordsOut, 
Meter bytesLocalIn, Meter by
                this.numBytesOutPerSecond = bytesOut.getRate();
        }
     
    +   public IOMetrics(
    +                   int numBytesInLocal, int numBytesInRemote, int 
numBytesOut, int numRecordsIn, int numRecordsOut,
    +                   double numBytesInLocalPerSecond, double 
numBytesInRemotePerSecond, double numBytesOutPerSecond,
    +                   double numRecordsInPerSecond, double 
numRecordsOutPerSecond) {
    --- End diff --
    
    I'm not sure whether this line breaking pattern is consistent.


> IOMetrics transfer through ExecGraph does not work for failed jobs
> ------------------------------------------------------------------
>
>                 Key: FLINK-5645
>                 URL: https://issues.apache.org/jira/browse/FLINK-5645
>             Project: Flink
>          Issue Type: Bug
>          Components: Metrics, Webfrontend
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Blocker
>
> While a job is running the web-interface polls IO metrics using the 
> MetricFetcher/MetricQueryService. For finished jobs these metrics are stored 
> in the ExecutionGraph; each vertex has an IOMetrics object; basically a 
> snapshot taken when the task was finished. 
> For completed jobs this mechanism is working. However, for failed jobs it 
> doesn't; in this case last fetched metrics are displayed.
> This isn't intended behavior and should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to