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

Chesnay Schepler closed FLINK-11183.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.1
                   1.9.0

master: d9803ac0ff590f532a2553c96e0462d7b30c7435

1.8: 977616242c5023021ac30a9be730e2989a18e6b8

1.7: e10a98f56ed89d1a50c0a0c9cb6fc5ba0d8f190f

> Heap/NonHeap memory metrics broken
> ----------------------------------
>
>                 Key: FLINK-11183
>                 URL: https://issues.apache.org/jira/browse/FLINK-11183
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Metrics
>    Affects Versions: 1.7.0
>            Reporter:  Mario Georgiev
>            Assignee: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.3, 1.9.0, 1.8.1
>
>         Attachments: memory.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Hello, 
> After upgrading from Flink 1.5.3 to Flink 1.7.0 graphite metrics for memory 
> started reporting wrong numbers. All the jobs are reporting the same memory 
> used. Off heap memory, direct memory, mapped memory is almost the same across 
> all our jobs, for heap memory used all jobs report memory used ~ 30mb? Is 
> that even correct, we've had jobs that die sporadically and it appears they 
> are OOM-ing, but we can't really see it and verify it because of the metrics.
> Was there any major change to the metrics collection in flink-graphite-1.7.0? 
>  
> You can see from the screenshot that it appears all our jobs are using same 
> memory. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to