You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/01/01 10:40:00 UTC
[jira] [Updated] (FLINK-7401) EnvironmentInformation.getMaxJvmHeapMemory does not return the value given via -Xmx
[ https://issues.apache.org/jira/browse/FLINK-7401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-7401:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned (was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
> EnvironmentInformation.getMaxJvmHeapMemory does not return the value given via -Xmx
> -----------------------------------------------------------------------------------
>
> Key: FLINK-7401
> URL: https://issues.apache.org/jira/browse/FLINK-7401
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.2.0, 1.2.1, 1.3.0, 1.3.1, 1.3.2, 1.4.0
> Reporter: Nico Kruber
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned
>
> {{EnvironmentInformation.getMaxJvmHeapMemory}} is intended to return the value given to the JVM via {{-Xmx}} but it actually returns something a bit smaller which may disturb memory calculations expecting the right value.
> For now, this is a "good" bug as the calculations inside {{TaskManagerServices#calculateNetworkBufferMemory()}}, for example, lead to lower values for the network buffers or the manages memory fractions which thus still fit into the bounds set by the JVM options.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)