[
https://issues.apache.org/jira/browse/MAPREDUCE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195185#comment-13195185
]
Eli Collins commented on MAPREDUCE-3736:
----------------------------------------
bq. fs.default.name is added to core-default.xml, where fs.defaultFS lives now
too.
Sorry, I meant why do we need to add fs.default.name back to core-default.xml,
so the non-MR users like Sqoop will have not have to modify their mini MR
cluster configs to set it manually? Ie is the mapreduce.job.hdfs-servers change
sufficient or do they also require fs.default.name be set?
> Variable substitution depth too large for fs.default.name causes jobs to fail
> -----------------------------------------------------------------------------
>
> Key: MAPREDUCE-3736
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3736
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.1
> Reporter: Eli Collins
> Assignee: Ahmed Radwan
> Priority: Blocker
> Attachments: MAPREDUCE-3736.patch, MAPREDUCE-3736_rev2.patch
>
>
> I'm seeing the same failure as MAPREDUCE-3462 in downstream projects running
> against a recent build of branch-23. MR-3462 modified the tests rather than
> fixing the framework. In that jira Ravi mentioned "I'm still ignorant of the
> change which made the tests start to fail. I should probably understand
> better the reasons for that change before proposing a more generalized fix."
> Let's figure out the general fix (rather than require all projects to set
> mapreduce.job.hdfs-servers in their conf we should fix this in the
> framework). Perhaps we should not default this config to "$fs.default.name"?
--
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
