[
https://issues.apache.org/jira/browse/HDFS-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906172#comment-13906172
]
Yongjun Zhang commented on HDFS-5939:
-------------------------------------
Thanks [~wheat9] and [~szetszwo].
Based on your input, sounds like we can do the alternative solution as I
mentioned in my last update
"Another alternative to my fix is, to change the interface of
NetworkTopology.chooseRandom exception spec, and to let it throw
NodatanodeException instead of InvalidArgumentException when numOfDataNode is
0".
<code>
public Node chooseRandom(String scope) throws NoDatanodeException
private Node chooseRandom(String scope, String excludedScope) throws
NoDatanodeException
</code>
If you agree, I will post a new patch with this change.
Thanks,
> WebHdfs returns misleading error code and logs nothing if trying to create a
> file with no DNs in cluster
> --------------------------------------------------------------------------------------------------------
>
> Key: HDFS-5939
> URL: https://issues.apache.org/jira/browse/HDFS-5939
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.3.0
> Reporter: Yongjun Zhang
> Assignee: Yongjun Zhang
> Attachments: HDFS-5939.001.patch
>
>
> When trying to access hdfs via webhdfs, and when datanode is dead, user will
> see an exception below without any clue that it's caused by dead datanode:
> $ curl -i -X PUT
> ".../webhdfs/v1/t1?op=CREATE&user.name=<userName>&overwrite=false"
> ...
> {"RemoteException":{"exception":"IllegalArgumentException","javaClassName":"java.lang.IllegalArgumentException","message":"n
> must be positive"}}
> Need to fix the report to give user hint about dead datanode.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
