hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramya Sunil (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-3763) Failed refreshQueues due to misconfiguration prevents further refreshing of queues
Date Mon, 30 Jan 2012 23:11:10 GMT
Failed refreshQueues due to misconfiguration prevents further refreshing of queues
----------------------------------------------------------------------------------

                 Key: MAPREDUCE-3763
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3763
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: mrv2
    Affects Versions: 0.23.1
            Reporter: Ramya Sunil
             Fix For: 0.23.1


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

        

Mime
View raw message