Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 13 Nov 2013 00:39:17 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12678806.1384266029464.62024.1384303157808@arcas>
In-Reply-To: <JIRA.12678806.1384266029464@arcas>
References: <JIRA.12678806.1384266029464@arcas>
Subject: [jira] [Commented] (YARN-1404) Add support for unmanaged containers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur commented on YARN-1404:
------------------------------------------

I've started working out on a patch that takes NULL as no process instead of the constant but NPEs pop all over the code as i keep guarding against them. I'm inclined to either keep the constant in the public API, and rename it to {{NO_PROCESS}}. Or if we want to have NULL in the API, in the NM on NULL arrival use a private {{NO_PROCESS}} constant.

> Add support for unmanaged containers
> ------------------------------------
>
>                 Key: YARN-1404
>                 URL: https://issues.apache.org/jira/browse/YARN-1404
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager
>    Affects Versions: 2.2.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: YARN-1404.patch
>
>
> Currently a container allocation requires to start a container process with the corresponding NodeManager's node.
> For applications that need to use the allocated resources out of band from Yarn this means that a dummy container process must be started.
> Impala/Llama is an example of such application which is currently starting a 'sleep 10y' (10 years) process as the container process. And the resource capabilities are used out of by and the Impala process collocated in the node. The Impala process ensures the processing associated to that resources do not exceed the capabilities of the container. Also, if the container is lost/preempted/killed, Impala stops using the corresponding resources.
> In addition, in the case of Llama, the current requirement of having a container process, gets complicates when hard resource enforcement (memory -ContainersMonitor- or cpu -via cgroups-) is enabled because Impala/Llama request resources with CPU and memory independently of each other. Some requests are CPU only and others are memory only. Unmanaged containers solve this problem as there is no underlying process with zero CPU or zero memory.


--
This message was sent by Atlassian JIRA
(v6.1#6144)