You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/01/15 10:17:00 UTC
[jira] [Updated] (FLINK-15597) Relax sanity check of JVM memory
overhead to be within its min/max
[ https://issues.apache.org/jira/browse/FLINK-15597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-15597:
-----------------------------------
Labels: pull-request-available (was: )
> Relax sanity check of JVM memory overhead to be within its min/max
> ------------------------------------------------------------------
>
> Key: FLINK-15597
> URL: https://issues.apache.org/jira/browse/FLINK-15597
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration, Runtime / Task
> Reporter: Andrey Zagrebin
> Assignee: Xintong Song
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.10.0
>
>
> When the explicitly configured process and Flink memory sizes are verified with the JVM meta space and overhead, JVM overhead does not have to be the exact fraction.
> It can be just within its min/max range, similar to how it is now for network/shuffle memory check after FLINK-15300.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)