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

Chuan Liu commented on YARN-2190:
---------------------------------

bq. 1. what would the implications for the move windows 8 for the API? What 
does it mean for server versions and builds?

If we want to continue supporting Windows 7 and Windows Server 2008R2 as 
default OS version, I can make Windows 8 build optional. Because Windows 7 does 
not support set CPU limits on job objects, the CPU limit feature will be absent 
in the Windows 7 build.

bq. 2. something is cutting off all the ASF copyright comments ... probably the 
IDE. That'll have the RAT tool complaining. It may be something to ignore 
during iterative development , but would need to be fixed before committing

Thanks for pointing out this. I will fix it in the new patch.

bq. 3. would it be possible to have a command line like

Yes. This is a very good suggestion!

> Provide a Windows container executor that can limit memory and CPU
> ------------------------------------------------------------------
>
>                 Key: YARN-2190
>                 URL: https://issues.apache.org/jira/browse/YARN-2190
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager
>            Reporter: Chuan Liu
>         Attachments: YARN-2190-prototype.patch
>
>
> Yarn default container executor on Windows does not set the resource limit on 
> the containers currently. The memory limit is enforced by a separate 
> monitoring thread. The container implementation on Windows uses Job Object 
> right now. The latest Windows (8 or later) API allows CPU and memory limits 
> on the job objects. We want to create a Windows container executor that sets 
> the limits on job objects thus provides resource enforcement at OS level.
> http://msdn.microsoft.com/en-us/library/windows/desktop/ms686216(v=vs.85).aspx



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

Reply via email to