[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194281#comment-13194281
 ] 

Eli Collins commented on MAPREDUCE-3736:
----------------------------------------

Ahmed and I investigated this some, it looks like core-default.xml has switched 
from  fs.default.name to fs.defaultFS however MR is still using fs.default.name 
which is now undefined. Seems like we should either update MR to use 
fs.defaultFS or define both fs.default.name and fs.defaultFS in core-site.xml
                
> 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
>
> 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

        

Reply via email to