[
https://issues.apache.org/jira/browse/HDFS-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802356#comment-13802356
]
Aaron T. Myers commented on HDFS-5403:
--------------------------------------
For reference, this results in an error like the following:
{quote}
java.lang.NullPointerException
at org.apache.hadoop.hdfs.web.JsonUtil.toDatanodeInfo(JsonUtil.java:305)
at org.apache.hadoop.hdfs.web.JsonUtil.toDatanodeInfoArray(JsonUtil.java:348)
at org.apache.hadoop.hdfs.web.JsonUtil.toLocatedBlock(JsonUtil.java:377)
at org.apache.hadoop.hdfs.web.JsonUtil.toLocatedBlockList(JsonUtil.java:413)
at org.apache.hadoop.hdfs.web.JsonUtil.toLocatedBlocks(JsonUtil.java:446)
at
org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getFileBlockLocations(WebHdfsFileSystem.java:1063)
at org.apache.hadoop.fs.FileSystem$4.next(FileSystem.java:1812)
at org.apache.hadoop.fs.FileSystem$4.next(FileSystem.java:1797)
{quote}
> WebHdfs client cannot communicate with older WebHdfs servers post HDFS-5306
> ---------------------------------------------------------------------------
>
> Key: HDFS-5403
> URL: https://issues.apache.org/jira/browse/HDFS-5403
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 2.2.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
>
> HDFS-5306 introduced the field infoSecurePort to the DatanodeIDProto PB
> definition and made it optional for compatibility purposes. However, we don't
> correctly the handle the case when this field is not present when
> deserializing the response from a WebHdfs request. This results in an NPE at
> the client when this occurs.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
