[
https://issues.apache.org/jira/browse/FLINK-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-2235.
---------------------------------
Resolution: Fixed
Assignee: Maximilian Michels
Fix Version/s: 0.10
Fixed via 910e8c438477f27c6d20392d00dd0cfbe8496c8b and
b0b0cb50d63e2f831196fc9219858467a07d8302
> Local Flink cluster allocates too much memory
> ---------------------------------------------
>
> Key: FLINK-2235
> URL: https://issues.apache.org/jira/browse/FLINK-2235
> Project: Flink
> Issue Type: Bug
> Components: Local Runtime, TaskManager
> Affects Versions: 0.9
> Environment: Oracle JDK: 1.6.0_65-b14-462
> Eclipse
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Fix For: 0.10
>
>
> When executing a Flink job locally, the task manager gets initialized with an
> insane amount of memory. After a quick look in the code it seems that the
> call to {{EnvironmentInformation.getSizeOfFreeHeapMemoryWithDefrag()}}
> returns a wrong estimate of the heap memory size.
> Moreover, the same user switched to Oracle JDK 1.8 and that made the error
> disappear. So I'm guessing this is some Java 1.6 quirk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
