[
https://issues.apache.org/jira/browse/FLINK-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125474#comment-15125474
]
Stephan Ewen commented on FLINK-2803:
-------------------------------------
Nice to hear to you want to contribute!
Flink has three portions of memory:
1. The network buffer memory
2. The Flink-managed memory for sorts/hashes/etc
3. The remainder
In the case where managed memory should be allocated off-heap, (1) & (2) will
not be on the heap, i.e. the heap will be as small as (3) alone. The JVM needs
to be started with the appropriate settings, both in standalone mode and in the
case of YARN.
The tests should verify that the settings for heap size, max direct memory (off
heap memory), and the config parameters are correctly set in all cases.
To make things more complicated, there is a flag that tells Flink whether to
allocate the memory from (2) immediately on startup, or lazily, when first
needed. The default is lazy.
> Add test case for Flink's memory allocation
> -------------------------------------------
>
> Key: FLINK-2803
> URL: https://issues.apache.org/jira/browse/FLINK-2803
> Project: Flink
> Issue Type: Test
> Components: Start-Stop Scripts, TaskManager, YARN Client
> Affects Versions: 0.9, 0.10.0
> Reporter: Maximilian Michels
> Priority: Minor
> Fix For: 1.0.0
>
>
> We need a test case which checks the correct memory settings for heap and
> off-heap memory allocation.
> Memory is calculated in
> 1. The startup scripts ({{taskmanager.sh}})
> 2. The ({{TaskManager}})
> 3. The YARN {{ApplicationMasterActor}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
