[
https://issues.apache.org/jira/browse/HDFS-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920014#comment-13920014
]
stack commented on HDFS-6047:
-----------------------------
The three failures are not related (you have to enable hedged reads, this is a
small fix for a NPE only, and the failures are from other domains altogether).
I've run this patch through QA three times. Twice, it failed with not tests
failed (zombies?), and this last time we have unrelated fails. Going to commit.
> TestPread NPE inside in DFSInputStream hedgedFetchBlockByteRange
> ----------------------------------------------------------------
>
> Key: HDFS-6047
> URL: https://issues.apache.org/jira/browse/HDFS-6047
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: stack
> Assignee: stack
> Fix For: 2.4.0
>
> Attachments: HDFS-6047.txt, HDFS-6047.txt, HDFS-6047.txt
>
>
> Our [~andrew.wang] saw this on internal test cluster running trunk:
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.hadoop.hdfs.DFSInputStream.hedgedFetchBlockByteRange(DFSInputStream.java:1181)
> at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:1296)
> at org.apache.hadoop.fs.FSInputStream.readFully(FSInputStream.java:78)
> at
> org.apache.hadoop.fs.FSDataInputStream.readFully(FSDataInputStream.java:108)
> at org.apache.hadoop.hdfs.TestPread.pReadFile(TestPread.java:151)
> at
> org.apache.hadoop.hdfs.TestPread.testMaxOutHedgedReadPool(TestPread.java:292)
> {code}
> TestPread was failing.
> The NPE comes of our presuming there always a chosenNode as we set up hedged
> reads inside in hedgedFetchBlockByteRange (chosenNode is null'd each time
> through the loop). Usually there is a chosenNode but need to allow for case
> where there is not.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
