[
https://issues.apache.org/jira/browse/YARN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy moved MAPREDUCE-3763 to YARN-27:
----------------------------------------------
Fix Version/s: (was: 0.24.0)
0.23.3
2.1.0-alpha
Component/s: (was: mrv2)
Affects Version/s: (was: 0.23.1)
Workflow: jira (was: no-reopen-closed, patch-avail)
Key: YARN-27 (was: MAPREDUCE-3763)
Project: Hadoop YARN (was: Hadoop Map/Reduce)
> 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
>
>
> 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
