Steve Loughran commented on YARN-2190:

# what would the implications for the move windows 8 for the API? What does it 
mean for server versions and builds?
# 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
# would it be possible to have a command line like
task create --memory 2048 name command-line
so that new options could go in (--cpu, --io) without confusion...the current 
approach looks a bit brittle

> 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

Reply via email to