[
https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172226#comment-15172226
]
Arun Suresh commented on YARN-2883:
-----------------------------------
Friday, February 26, 2016
5:01 PM
*ContainersMonitorImpl*
* In {{startPendingContainers()}}, It looks like the synchronized block itself
can be refactored into another function, and then you can call the function
first with {{queueGuarRequests}} and then with {{queueOpportRequests}}
* W.r.t TODO before {{updateNMTokenIdentifier}}.. Yup, it needs to be there for
all containers* W.r.t TODO inside the CHANGE_MONITORING_CONTAINER_RESOURCE,
yup, think we might have to update the available resource
* Looks like {{setQueuedContainerStatus}} method is not being used
Also, looks like a lot of tests have failed. Can you please verify if this is
not due to changes in this patch.
> Queuing of container requests in the NM
> ---------------------------------------
>
> Key: YARN-2883
> URL: https://issues.apache.org/jira/browse/YARN-2883
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Konstantinos Karanasos
> Assignee: Konstantinos Karanasos
> Attachments: YARN-2883-yarn-2877.001.patch
>
>
> We propose to add a queue in each NM, where queueable container requests can
> be held.
> Based on the available resources in the node and the containers in the queue,
> the NM will decide when to allow the execution of a queued container.
> In order to ensure the instantaneous start of a guaranteed-start container,
> the NM may decide to pre-empt/kill running queueable containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
