[jira] [Closed] (FLINK-10951) Disable enforcing of YARN container virtual memory limits in tests

["Gary Yao (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Yao closed FLINK-10951.
----------------------------
    Resolution: Fixed

Fixed via
1.8 33f3de010c59897e9ec9277484195e2845e8a5f6
1.7 70623d3f7f40f382bca26b3ba8c9cf0d9ffb63eb
1.6 929d9e05f5a66ec21f7bc6c4ad5e7ee10ab54332

> Disable enforcing of YARN container virtual memory limits in tests
> ------------------------------------------------------------------
>
>                 Key: FLINK-10951
>                 URL: https://issues.apache.org/jira/browse/FLINK-10951
>             Project: Flink
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 1.8.0
>            Reporter: Gary Yao
>            Assignee: Gary Yao
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.6.3, 1.8.0, 1.7.1
>
>
> *Description*
> The Jepsen YARN tests sporadically fail because TM containers are exceeding their virtual memory limits:
> {noformat}
> Closing TaskExecutor connection container_1541436244107_0001_01_000005 because: Container [pid=32403,containerID=container_1541436244107_0001_01_000005] is running beyond virtual memory limits. Current usage: 970.2 MB of 2 GB physical memory used; 4.2 GB of 4.2 GB virtual memory used. Killing container.
> {noformat}
> By default YARN enforces a virtual memory limit of 2.1 times the requested physical memory. However, in my experiments, the virtual memory of a JVM process running the {{ClusterEntryPoint}} (without submitting job) is already in the region of 3.3 GB. Hence, the virtual memory enforcement should be disabled.
> *Acceptance Criteria*
> * {{yarn.nodemanager.vmem-check-enabled}} is {{false}} in {{yarn-site.xml}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)