[
https://issues.apache.org/jira/browse/YARN-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148306#comment-15148306
]
Akira AJISAKA commented on YARN-2225:
-------------------------------------
I'm thinking the default value should be changed in branch-2 as well. We did
some incompatible changes in branch-2 if the change is really needed. There are
14 incompatible changes in 2.6.0/2.7.0.
https://issues.apache.org/jira/issues/?jql=project%20in%20(YARN%2C%20HADOOP%2C%20HDFS%2C%20MAPREDUCE)%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20in%20(2.6.0%2C%202.7.0)%20AND%20%22Hadoop%20Flags%22%20%3D%20%22Incompatible%20change%22
I fed up with hearing Java8 users' complaints, "The default value does not
work.".
> 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.3.4#6332)
