[
https://issues.apache.org/jira/browse/FLINK-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725735#comment-16725735
]
Mario Georgiev commented on FLINK-11183:
-----------------------------------------
Hello,
Using the System Metrics would be quite useless, because we have our
taskmanagers/jobmanagers in docker. Using 1 Job Manager per Job and multiple
Task Managers.
This is the Grafana Query we are using, it should be relating to the
taskmanagers?
aliasByNode(HIDDEN.*-flink.$env.*.*.HIDDEN.*.Status.JVM.Memory.Heap.Used, 3, 11)
On 1.5.3 the memory was shown correctly, we were not using legacy mode as far
as i know.
> Flink 1.7.0 wrong memory graphite metrics
> -----------------------------------------
>
> Key: FLINK-11183
> URL: https://issues.apache.org/jira/browse/FLINK-11183
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.7.0
> Reporter: Mario Georgiev
> Priority: Minor
> Attachments: memory.png
>
>
> 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)
