hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-27) Failed refreshQueues due to misconfiguration prevents further refreshing of queues
Date Mon, 20 Aug 2012 16:15:38 GMT

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

Hudson commented on YARN-27:

Integrated in Hadoop-Common-trunk-Commit #2605 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2605/])
    YARN-27. Fixed location of ms.start call (Revision 1375083)

     Result = SUCCESS
tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375083
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestQueueMetrics.java

> Failed refreshQueues due to misconfiguration prevents further refreshing of queues
> ----------------------------------------------------------------------------------
>                 Key: YARN-27
>                 URL: https://issues.apache.org/jira/browse/YARN-27
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Ramya Sunil
>            Assignee: Arun C Murthy
>             Fix For: 2.1.0-alpha, 0.23.3
>         Attachments: YARN-27.patch
> Stumbled upon this problem while refreshing queues with incorrect configuration. The
exact scenario was:
> 1. Added a new queue "newQueue" without defining its capacity.
> 2. "bin/mapred queue -refreshQueues" fails correctly with "Illegal capacity of -1 for
queue root.newQueue"
> 3. However, after defining the capacity of "newQueue" followed by a second "bin/mapred
queue -refreshQueues" throws "org.apache.hadoop.metrics2.MetricsException: Metrics source
QueueMetrics,q0=root,q1=newQueue already exists!" Also see Hadoop:name=QueueMetrics,q0=root,q1=newQueue,service=ResourceManager
metrics being available even though the queue was not added.
> The expected behavior would be to refresh the queues correctly and allow addition of

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message