[ https://issues.apache.org/jira/browse/YARN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437939#comment-13437939
]
Thomas Graves commented on YARN-27:
-----------------------------------
+1 with minor change to remove extra "ms.start()" from TestQueueMetrics
Thanks Arun!
> 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
"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
|