Varun Vasudev commented on YARN-160:

The change for the Windows cpu limits fixes a bug in the current 
implementation. The current implementation allows YARN containers to exceed the 
configured cpu limit in some cases.

> nodemanagers should obtain cpu/memory values from underlying OS
> ---------------------------------------------------------------
>                 Key: YARN-160
>                 URL: https://issues.apache.org/jira/browse/YARN-160
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.0.3-alpha
>            Reporter: Alejandro Abdelnur
>            Assignee: Varun Vasudev
>              Labels: BB2015-05-TBR
>         Attachments: YARN-160.005.patch, YARN-160.006.patch, 
> YARN-160.007.patch, YARN-160.008.patch, apache-yarn-160.0.patch, 
> apache-yarn-160.1.patch, apache-yarn-160.2.patch, apache-yarn-160.3.patch
> As mentioned in YARN-2
> *NM memory and CPU configs*
> Currently these values are coming from the config of the NM, we should be 
> able to obtain those values from the OS (ie, in the case of Linux from 
> /proc/meminfo & /proc/cpuinfo). As this is highly OS dependent we should have 
> an interface that obtains this information. In addition implementations of 
> this interface should be able to specify a mem/cpu offset (amount of mem/cpu 
> not to be avail as YARN resource), this would allow to reserve mem/cpu for 
> the OS and other services outside of YARN containers.

This message was sent by Atlassian JIRA

Reply via email to