Vinod Kumar Vavilapalli commented on YARN-2225:

It breaks compatibility w.r.t behavior - asking existing users who care about 
it to turn it on explicitly.

bq. In spirit, virtual memory check has been a pain and we end up recommending 
users to turn it off.
I have had a different experience. It indeed is a pain for testing both in 
Hadoop and in high level frameworks, but it's been invaluable in real life 
clusters to thwart run away jobs - specifically the non-java ones - from 
affecting the cluster.

> 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

Reply via email to