[ 
https://issues.apache.org/jira/browse/YARN-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chuan Liu updated YARN-2190:
----------------------------
    Attachment: YARN-2190.11.patch

[~vvasudev], thanks for review! All you comments should have been addressed.

bq. 1. What about WindowsSecureContainerExecutor? Does this feature not apply 
to secure environments?

As my previous comment noted. This patch does not apply to 
WindowsSecureContainerExecutor and secure environments. We can address secure 
environment in a separate JIRA.

[~rusanu], thanks for the note! The new patch was using CLRF in vcxproj files. 
Hope it will pass this time.

> 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
>            Assignee: Chuan Liu
>         Attachments: YARN-2190-prototype.patch, YARN-2190.1.patch, 
> YARN-2190.10.patch, YARN-2190.11.patch, YARN-2190.2.patch, YARN-2190.3.patch, 
> YARN-2190.4.patch, YARN-2190.5.patch, YARN-2190.6.patch, YARN-2190.7.patch, 
> YARN-2190.8.patch, YARN-2190.9.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.3.4#6332)

Reply via email to