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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693401#comment-16693401 ] 

ASF GitHub Bot commented on FLINK-10951:
----------------------------------------

GJL opened a new pull request #7149: [FLINK-10951][tests] Set yarn.nodemanager.vmem-check-enabled to false
URL: https://github.com/apache/flink/pull/7149
 
 
   ## What is the purpose of the change
   
   *The Jepsen YARN tests sporadically fail because TM containers are exceeding their virtual memory limits. This PR disables the virtual memory check.*
   
   
   ## Brief change log
   
     - *Set yarn.nodemanager.vmem-check-enabled to false*
     - *Re-order config keys alphabetically*
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as *Jepsen test suite*.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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.8.0
>
>
> *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)