[
https://issues.apache.org/jira/browse/MAPREDUCE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837649#action_12837649
]
Hong Tang commented on MAPREDUCE-1527:
--------------------------------------
I rerun the test and now I noticed the following message:
"10/02/23 22:23:05 WARN mapred.DeprecatedQueueConfigurationParser: Configuring
"mapred.queue.names" in mapred-site.xml or hadoop-site.xml is deprecated.
Configure queue hierarchy in mapred-queues.xml".
Looking back to reconstruct our thoughts - I believe we probably ignored this
message, which is among the many similar warnings about deprecated keys in the
conf file. Since we do put a properly formatted mapred-queues.xml in the
classpath, we thought mapred-queues.xml should be loaded. I think the warning
message could be more explicit, e.g. "Confiure queue hierarchy in
mapred-queues.xml and remove "mapred.queue.names" from mapred-site.xml". Or
"mapred-queues.xml will be ignored since you have "mapred.queue.names" defined
in mapred-site.xml".
> QueueManager should issue warning if mapred-queues.xml is skipped.
> ------------------------------------------------------------------
>
> Key: MAPREDUCE-1527
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1527
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Hong Tang
>
> MAPREDUCE-861 added support for hierarchical queues and used a new file
> mapred-queues.xml to configure queues. But the QueueManager will silently
> skip the file if property "mapred.queue.names" is defined in Configuration.
> This tripped us when we are testing MAPREDUCE-1235 and copied configuration
> files from a Hadoop 0.20 cluster.
> I suggest QueueManager issue a friendly warning if both of the following are
> true: (1) "mapred.queue.names" exists in Configuration; (2)
> "mapred-queues.xml" is found in the classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
