hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zheng Shao (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3918) Improve fuse-dfs error message when classpath not set or set incorrectly
Date Mon, 11 Aug 2008 22:14:46 GMT

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

Zheng Shao commented on HADOOP-3918:

The hadoop jar filename looks like hadoop-0.19.0-dev-core.jar, but we are looking for "hadoop-.+?.jar".

Shall we look for "hadoop-.*-dev-core\\.jar" instead?

> Improve fuse-dfs error message when classpath not set or set incorrectly
> ------------------------------------------------------------------------
>                 Key: HADOOP-3918
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3918
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/fuse-dfs
>            Reporter: Pete Wyckoff
>            Assignee: Pete Wyckoff
>            Priority: Minor
>         Attachments: patch0.txt, patch1.txt, patch1.txt
> Currently libhdfs does an exit(1) when it cannot create a hadoop object. fuse does not
like this and instead fuse_dfs should return -EIO and log to syslog and stderr a message.
Also if it is obvious somehting is wrong, like the CLASSPATH is null or does not contain something
of the form hadoop-[a-zA-Z-].jar immediately print an error and exit
> Note that it is tough to debug this issue because when fuse-dfs is not in debug mode,
it is running as a fuse module and stderr is redirected, so all one gets is "software abort"
when libhdfs exits. So, this will greatly improve things since fuse-dfs can print a proper
error and the user can quickly see what the problem is.

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

View raw message