[
https://issues.apache.org/jira/browse/HADOOP-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668259#action_12668259
]
Raghu Angadi commented on HADOOP-4862:
--------------------------------------
output from test-patch : {noformat}
[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
{noformat}
I have manually tested this and is relatively a minor issues. I don't think it
needs a test case.
> A spurious IOException log on DataNode is not completely removed
> ----------------------------------------------------------------
>
> Key: HADOOP-4862
> URL: https://issues.apache.org/jira/browse/HADOOP-4862
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.2
> Environment: Minor : HADOOP-3678 did not remove all the cases of
> spurious IOExceptions logged by DataNode.
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Priority: Blocker
> Fix For: 0.19.1
>
> Attachments: HADOOP-4862-branch-18.patch, HADOOP-4862.patch,
> HADOOP-4862.patch
>
>
> HADOOP-3678 fixes a spurious warning log in DataNode, in most cases. This log
> is still possible in some cases.
> For e.g. The exception is still logged if the client closes the connection
> after DataNode writes all the block data but before it writes final 4 bytes
> to indicate end of data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
