[
https://issues.apache.org/jira/browse/HADOOP-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615787#action_12615787
]
Hadoop QA commented on HADOOP-3778:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386648/HADOOP-3778.patch
against trunk revision 678845.
+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 tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2922/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2922/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2922/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2922/console
This message is automatically generated.
> seek(long) in DFSInputStream should catch socket exception for retry later
> --------------------------------------------------------------------------
>
> Key: HADOOP-3778
> URL: https://issues.apache.org/jira/browse/HADOOP-3778
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: LN
> Assignee: LN
> Priority: Minor
> Fix For: 0.19.0
>
> Attachments: HADOOP-3778.patch, HADOOP-3778.patch, HADOOP-3778.patch
>
>
> HADOOP-2346 introduced data read/write timeout. when data stream borken,
> DFSClient will retry in read/write methods, but no such mechanism found when
> seek(long) calling blockReader.skip(diff) (DFSClient.java #1582), will let
> IOException throw to application. i met NPE when using MapFile in hbase.
> i'm supposing in the seek(long) method, let done be 'false' will causing
> retry (via 'blockEnd = -1'), a patch will attached later for review.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
