[
https://issues.apache.org/jira/browse/HDFS-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993956#comment-13993956
]
Hadoop QA commented on HDFS-5522:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12644147/HDFS-5522-v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests 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/6869//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6869//console
This message is automatically generated.
> Datanode disk error check may be incorrectly skipped
> ----------------------------------------------------
>
> Key: HDFS-5522
> URL: https://issues.apache.org/jira/browse/HDFS-5522
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.9, 2.2.0
> Reporter: Kihwal Lee
> Assignee: Rushabh S Shah
> Attachments: HDFS-5522-v2.patch, HDFS-5522-v3.patch, HDFS-5522.patch
>
>
> After HDFS-4581 and HDFS-4699, {{checkDiskError()}} is not called when
> network errors occur during processing data node requests. This appears to
> create problems when a disk is having problems, but not failing I/O soon.
> If I/O hangs for a long time, network read/write may timeout first and the
> peer may close the connection. Although the error was caused by a faulty
> local disk, disk check is not being carried out in this case.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
