[
https://issues.apache.org/jira/browse/HADOOP-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-4862:
---------------------------------
Environment: Minor : HADOOP-3678 did not remove all the cases of spurious
IOExceptions logged by DataNode.
Summary: A spurious IOException log on DataNode is not completely
removed (was: A spuriou IOException log on DataNode is not completely removed)
> 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.
