hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2225) Turn the virtual memory check to be off by default
Date Fri, 27 Jun 2014 22:41:25 GMT

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

Vinod Kumar Vavilapalli commented on YARN-2225:
-----------------------------------------------

-1 for changing the default.. This breaks compatibility.

bq. The virtual memory check may not be the best way to isolate applications. Virtual memory
is not the constrained resource.
I still see a lot of apps that needs isolation w.r.t vmem.

It's not about which resource is constrained, it is about isolation. We already identify physical
memory as constrained and use that as the main scheduling dimension. 

> 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)

Mime
View raw message