[
https://issues.apache.org/jira/browse/HDFS-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453863#comment-13453863
]
Hadoop QA commented on HDFS-3927:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544787/HDFS-3927.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. 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.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.TestDatanodeBlockScanner
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3180//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3180//console
This message is automatically generated.
> DFSInputStream#blockSeekTo may print incorrect warn msg for IOException
> -----------------------------------------------------------------------
>
> Key: HDFS-3927
> URL: https://issues.apache.org/jira/browse/HDFS-3927
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Priority: Minor
> Attachments: HDFS-3927.patch
>
>
> In DFSInputStream#blockSeekTo, for most IOExceptions (except
> InvalidEncryptionKeyException and InvalidBlockTokenException), the current
> code only prints "Failed to connect to targetAddr", which can be incorrect
> since there are other possible cases, e.g., the chosen node (remote/local)
> can be connected but the block/replica cannot be found. The correct error msg
> (including the error msg from remote node) should be printed to log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
