[
https://issues.apache.org/jira/browse/YARN-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490424#comment-14490424
]
Hadoop QA commented on YARN-3354:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12724668/YARN-3354.1.patch
against trunk revision 7660da9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7307//console
This message is automatically generated.
> Container should contains node-labels asked by original ResourceRequests
> ------------------------------------------------------------------------
>
> Key: YARN-3354
> URL: https://issues.apache.org/jira/browse/YARN-3354
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, capacityscheduler, nodemanager, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-3354.1.patch
>
>
> We proposed non-exclusive node labels in YARN-3214, makes non-labeled
> resource requests can be allocated on labeled nodes which has idle resources.
> To make preemption work, we need know an allocated container's original node
> label: when labeled resource requests comes back, we need kill non-labeled
> containers running on labeled nodes.
> This requires add node-labels in Container, and also, NM need store this
> information and send back to RM when RM restart to recover original container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
