[
https://issues.apache.org/jira/browse/HDFS-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918992#comment-13918992
]
Hadoop QA commented on HDFS-6047:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12632406/HDFS-6047.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 3 new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1
release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
hadoop-hdfs-project/hadoop-hdfs
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6287//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/6287//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/6287//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6287//console
This message is automatically generated.
> 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
>
>
> 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)
