[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820641#comment-13820641 ]
Alejandro Abdelnur commented on YARN-1404: ------------------------------------------ [~hitesh], We actually don't need the constant {{UNMANAGED_CONTAINER}}, we can just specify NULL and would mean not process associated to the container. [~bikassaha], I'm following YARN-1040 but it didn't strike me as related, specially as it cares about >1 processes. But in the way you position it can be as related. So, starting a container with a NULL {{ContainerLauncherContext}} would start the container life and avoid it from being timeout and claimed by the RM. Then this JIRA could be seen as a subtask of YARN-1040 that enables the zero process use case to be followed up by the reuse use case. Do you agree? > 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)