You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2009/12/22 17:48:29 UTC
[jira] Created: (HDFS-847) Improve fuse_dfs error when server !=
fs.default.name
Improve fuse_dfs error when server != fs.default.name
-----------------------------------------------------
Key: HDFS-847
URL: https://issues.apache.org/jira/browse/HDFS-847
Project: Hadoop HDFS
Issue Type: Bug
Components: contrib/fuse-dfs
Reporter: Eli Collins
Assignee: Eli Collins
Giving fuse_dfs a server name other than an exact match of fs.default.name results in cryptic errors. Let's make this scenario result in a better error message indicating what's up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HDFS-847) Improve fuse_dfs error when server !=
fs.default.name
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins resolved HDFS-847.
------------------------------
Resolution: Not A Problem
Already fixed on trunk. Giving fuse_dfs a host name that's an alias to what's in fs.default.name or the IP directly both works. Invalid hostname get an error unable to connect to the given host which is intelligible.
> Improve fuse_dfs error when server != fs.default.name
> -----------------------------------------------------
>
> Key: HDFS-847
> URL: https://issues.apache.org/jira/browse/HDFS-847
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: contrib/fuse-dfs
> Reporter: Eli Collins
> Assignee: Eli Collins
>
> Giving fuse_dfs a server name other than an exact match of fs.default.name results in cryptic errors. Let's make this scenario result in a better error message indicating what's up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.