[jira] [Comment Edited] (YARN-2225) Turn the virtual memory check to be off by default

["Karthik Kambatla (JIRA)" <ji...@apache.org>]

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

Karthik Kambatla edited comment on YARN-2225 at 6/27/14 10:48 PM:
------------------------------------------------------------------

According to our compatibility guide, "The default values of Hadoop-defined properties can be changed across minor/major releases, but will remain the same across point releases within a minor release."

So, in letter, we can't target 2.4.1 or 2.5.1, but can target 2.5 or 2.6. In spirit, virtual memory check has been a pain and we end up recommending users to turn it off. 


was (Author: kkambatl):
According to your compatibility guide, "The default values of Hadoop-defined properties can be changed across minor/major releases, but will remain the same across point releases within a minor release."

So, in letter, we can't target 2.4.1 or 2.5.1, but can target 2.5 or 2.6. In spirit, virtual memory check has been a pain and we end up recommending users to turn it off. 

> Turn the virtual memory check to be off by default
> --------------------------------------------------
>
>                 Key: YARN-2225
>                 URL: https://issues.apache.org/jira/browse/YARN-2225
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>         Attachments: YARN-2225.patch
>
>
> The virtual memory check may not be the best way to isolate applications. Virtual memory is not the constrained resource. It would be better if we limit the swapping of the task using swapiness instead. This patch will turn this DEFAULT_NM_VMEM_CHECK_ENABLED off by default and let users turn it on if they need to.



--
This message was sent by Atlassian JIRA
(v6.2#6252)