[ http://issues.apache.org/jira/browse/NUTCH-186?page=comments#action_12364010 ]
Gal Nitzan commented on NUTCH-186: ---------------------------------- After reading the code and I think I figured it... :) The issue of the mapred-default.xml is totaly misleading. Actualy : mapred.map.tasks and mapred.reduce.tasks properties does not have any effect when placed in mapred-default.xml (unless JobConf needs it which I didn´t check) because this file is loaded only when JobConf is constructed. But tasktracker is looking for these properties in nutch-site and not in mapred-default. If these properties does not exists in nutch-site.xm with the correct values for your system, these values will be picked from nutch-defaul.xml. Further, I am not sure that nutch-site.xml "overiding" everything should be the correct behavior. Most users knows that nutch-site.xml overides nutch-default but I think we should leave it up to them the option to override nutch-site and it will be a good start into breaking configuration to parts (ndfs and mapred are going to be seperated from nutch)... Gal > mapred-default.xml is over ridden by nutch-site.xml > --------------------------------------------------- > > Key: NUTCH-186 > URL: http://issues.apache.org/jira/browse/NUTCH-186 > Project: Nutch > Type: Bug > Versions: 0.8-dev > Environment: All > Reporter: Gal Nitzan > Priority: Minor > Attachments: myBeautifulPatch.patch, myBeautifulPatch.patch > > If mapred.map.tasks and mapred.reduce.tasks are defined in nutch-site.xml and > also in mapred-default.xml the definitions from nutch-site.xml are those that > will take effect. > So if a user mistakenly copies those entries into nutch-site.xml from the > nutch-default.xml she will not understand what happens. > I would like to propose removing these setting completely from the > nutch-default.xml and put it only in mapred-default.xml where it belongs. > I will be happy to supply a patch for that if the proposition accepted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
