Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
1.1.1, 1.1.2
-
None
-
None
Description
When we trying to check whether the target path exists in HDFS through webhdfs, if the given path to check doesn't exist, we will always observe warning message like:
===========================================================
13/04/21 04:38:01 WARN web.WebHdfsFileSystem: Original exception is
org.apache.hadoop.ipc.RemoteException: user = biadmin, proxyUser = null, path = /testWebhdfs
at org.apache.hadoop.hdfs.web.JsonUtil.toRemoteException(JsonUtil.java:114)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.validateResponse(WebHdfsFileSystem.java:294)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.access$500(WebHdfsFileSystem.java:103)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$Runner.getResponse(WebHdfsFileSystem.java:552)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$Runner.run(WebHdfsFileSystem.java:473)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.run(WebHdfsFileSystem.java:404)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getHdfsFileStatus(WebHdfsFileSystem.java:573)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getFileStatus(WebHdfsFileSystem.java:584)
at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:768)
===========================================================
while actually FileNotFoundException should be expected when the operation is GETFILESTATUS and target path doesn't exist. The fact that RemoteException didn't include the real exception class(FileNotFoundException) in its toString method even make the message more misleading, since from the message user won't know what the warning is about
Attachments
Attachments
Issue Links
- duplicates
-
HDFS-5245 shouldRetry() in WebHDFSFileSystem generates excessive warnings
- Resolved