hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-7056) NN unintentionally reads mapred-site.xml
Date Tue, 30 Nov 2010 20:52:11 GMT
NN unintentionally reads mapred-site.xml
----------------------------------------

                 Key: HADOOP-7056
                 URL: https://issues.apache.org/jira/browse/HADOOP-7056
             Project: Hadoop Common
          Issue Type: Bug
    Affects Versions: 0.22.0
            Reporter: Aaron T. Myers


It seems that {{mapred-site.xml}} is now unintentionally being read by the NN, and probably
all the daemons.

This is because the {{Groups}} constructor calls {{ReflectionUtils.newInstance(...)}}, which
in turn calls {{ReflectionUtils.setConf(...)}}, which calls {{ReflectionUtils.setJobConf(...)}},
which creates an instance of {{o.a.h.mapred.JobConf}}, which calls {{o.a.h.mapreduce.util.ConfigUtil.loadResources(...)}},
which reads in {{mapred-site.xml}} and {{mapred-default.xml}}. Phew!

I suspect the appropriate solution is for {{ReflectionUtils.setConf(...)}} to be changed to
not call (the mapred-specific) {{ReflectionUtils.setJobConf(...)}}, but there's a comment
in there which says it's being left in place for backward compatibility. Can somebody with
more knowledge of that situation please comment?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message