[
https://issues.apache.org/jira/browse/FLINK-21158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272790#comment-17272790
]
Xintong Song commented on FLINK-21158:
--------------------------------------
Thanks [~pengkangjing] for reporting this, and thanks [~RocMarshal] and
[~chesnay] for looking into this.
I think this is a valid problem. When implementing FLIP-49, we have not set
derived jvm metaspace/overhead sizes via dynamic properties, due to the
assumption that these values will not be used after the JVM process being
launched. This assumption is no longer true since in FLIP-102 we start to
display these configuration values on the web ui.
[~pengkangjing], the changes you proposed look good to me. I've assigned you to
this ticket. Please go ahead.
> wrong jvm metaspace and overhead size show in taskmanager metric page
> ----------------------------------------------------------------------
>
> Key: FLINK-21158
> URL: https://issues.apache.org/jira/browse/FLINK-21158
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Web Frontend
> Affects Versions: 1.12.0, 1.12.1
> Reporter: pengkangjing
> Assignee: pengkangjing
> Priority: Minor
> Attachments: image-2021-01-27-16-19-16-390.png,
> image-2021-01-27-16-30-51-834.png, image-2021-01-27-16-59-28-488.png,
> image-2021-01-27-17-33-25-300.png, image-2021-01-27-17-34-32-454.png,
> image-2021-01-27-18-07-16-558.png, image-2021-01-27-18-17-01-917.png,
> image-2021-01-27-18-18-18-241.png, image-2021-01-27-18-19-31-121.png,
> image-2021-01-27-18-31-07-616.png
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> the size of jvm metaspace and jvm overhead on taskmanager metrics page not
> the derived value from flink-conf.yaml but
> always be the default value.
> i used the defalut flink-conf.yaml
> default value:
> JVM_METASPACE - 256M
> JVM_OVERHEAD_MAX - 1GB
> !image-2021-01-27-16-30-51-834.png!
> !image-2021-01-27-16-19-16-390.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
