[
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-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-unassigned, stale-major
>
> {{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.3.4#803005)
