[HADOOP-3918] Improve fuse-dfs error message when classpath not set or set incorrectly

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Hadoop Flags: Incompatible change

Release Note

libhdfs will return NULL when there's a java exception creating an object rather than exiting immediately, so that the application can decide what to do on this kind of error.

• Assignee: Pete Wyckoff
• Reporter: Pete Wyckoff
• Created: 07/Aug/08 17:02
• Updated: 08/Jul/09 17:05
• Resolved: 16/Sep/08 01:48

Description

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.

Issue Links

• is part of: HADOOP-4106 add time, permission and user attribute support to fuse-dfs