hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5259) Job with output hdfs:/user/<username>/outputpath (no authority) fails with Wrong FS
Date Thu, 19 Feb 2009 20:12:01 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675114#action_12675114

Doug Cutting commented on HADOOP-5259:

I'm having trouble reproducing this in a unit test.  I think the only way you can get this
is if you set fs.default.name to hdfs://aaa.bbb.ccc:8020/ in your site config file.  Is that
what you've done?  If so, the workaround is to instead use just hdfs://aaa.bbb.ccc/ there.
 The problem is that the port-defaulting is filesystem specific, but the setting of the default
FS is generic, and hence knows nothing about port defaulting.

> Job with output hdfs:/user/<username>/outputpath (no authority) fails with Wrong
> -----------------------------------------------------------------------------------
>                 Key: HADOOP-5259
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5259
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs, fs
>    Affects Versions: 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.19.0
>            Reporter: Koji Noguchi
>            Assignee: Doug Cutting
> Using namenode with default port of 8020.
> When starting a job with output hdfs:/user/knoguchi/outputpath, my job fails with 
> Wrong FS: hdfs:/user/knoguchi/outputpath, expected: hdfs://aaa.bbb.cc

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

View raw message