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

Hadoop QA commented on YARN-2744:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12677087/YARN-2744-20141025-1.patch
  against trunk revision f44cf99.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5558//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5558//console

This message is automatically generated.

> Under some scenario, it is possible to end up with capacity scheduler 
> configuration that uses labels that no longer exist
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2744
>                 URL: https://issues.apache.org/jira/browse/YARN-2744
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>    Affects Versions: 2.5.1
>            Reporter: Sumit Mohanty
>            Assignee: Wangda Tan
>            Priority: Critical
>             Fix For: 2.6.0
>
>         Attachments: YARN-2744-20141025-1.patch
>
>
> Use the following steps:
> * Ensure default in-memory storage is configured for labels
> * Define some labels and assign nodes to labels (e.g. define two labels and 
> assign both labels to the host on a one host cluster)
> * Invoke refreshQueues
> * Modify capacity scheduler to create two top level queues and allow access 
> to the labels from both the queues
> * Assign appropriate "label + queue" specific capacities
> * Restart resource manager
> Noticed that RM starts without any issues. The labels are not preserved 
> across restart and thus the capacity-scheduler ends up using labels that are 
> no longer present.
> At this point submitting an application to YARN will not succeed as there are 
> no resources available with the labels.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to