[
https://issues.apache.org/jira/browse/FLINK-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386949#comment-14386949
]
Stephan Ewen commented on FLINK-1435:
-------------------------------------
I think we misunderstood this issue initially. This seems like the TaskManager
is started with a heap size that exceeds the physical memory of the machine. It
is possible to do that, if your OS has enough swap space.
The process "hangs", because it is incredibly slow doe to non-stop swapping.
Inside the JVM, you do not see that memory is missing, because it is not, it
only comes from the swap space.
This is not a Flink bug, such mis-configuration is well possible.
> TaskManager does not log missing memory error on start up
> ---------------------------------------------------------
>
> Key: FLINK-1435
> URL: https://issues.apache.org/jira/browse/FLINK-1435
> Project: Flink
> Issue Type: Bug
> Components: TaskManager
> Affects Versions: 0.7.0-incubating
> Reporter: Malte Schwarzer
> Priority: Minor
> Labels: memorymanager, starter
>
> When using bin/start-cluster.sh to start TaskManagers and a worker node is
> failing to start because of missing memory, you do not receive any error
> messages in log files.
> Worker node has only 15000M memory available, but it is configured with
> Maximum heap size: 40000 MiBytes. Task manager does not join the cluster.
> Process hangs.
> Last lines of log looks like this:
> ...
> ... - - Starting with 12 incoming and 12 outgoing connection threads.
> ... - Setting low water mark to 16384 and high water mark to 32768 bytes.
> ... - Instantiated PooledByteBufAllocator with direct arenas: 24, heap
> arenas: 0, page size (bytes): 65536, chunk size (bytes): 16777216.
> ... - Using 0.7 of the free heap space for managed memory.
> ... - Initializing memory manager with 24447 megabytes of memory. Page size
> is 32768 bytes.
> (END)
> Error message about not enough memory is missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
