[jira] Issue Comment Edited: (HADOOP-3918) Improve fuse-dfs error message when classpath not set or set incorrectly

["Pete Wyckoff (JIRA)" <ji...@apache.org>]

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

wyckoff edited comment on HADOOP-3918 at 9/6/08 3:43 PM:
--------------------------------------------------------------

If [https://issues.apache.org/jira/browse/HADOOP-3963] lihdfs returns null instead of exiting on error gets committed, maybe it's better to just try doing an hdfsConnect.  We can probably look at errno to try and see what the error is and if it's a JNI problem, output an appropriate message?



      was (Author: wyckoff):
    If [https://issues.apache.org/jira/browse/HADOOP-3963 lihdfs returns null instead of exiting on error] gets committed, maybe it's better to just try doing an hdfsConnect.  We can probably look at errno to try and see what the error is and if it's a JNI problem, output an appropriate message?


  
> 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
>             Fix For: 0.19.0
>
>         Attachments: patch0.txt, patch1.txt, patch1.txt, patch2.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.