You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2012/08/20 18:45:38 UTC
[jira] [Resolved] (YARN-27) Failed refreshQueues due to
misconfiguration prevents further refreshing of queues
[ https://issues.apache.org/jira/browse/YARN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Graves resolved YARN-27.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0-alpha
I committed this to trunk, branch-2, branch-2.1.0-alpha and branch-0.23
> 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, 2.2.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 "newQueue".
--
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