[HADOOP-4862] A spurious IOException log on DataNode is not completely removed

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.18.2
• Fix Version/s: 0.19.1

Environment

Minor : HADOOP-3678 did not remove all the cases of spurious IOExceptions logged by DataNode.

• Hadoop Flags: Reviewed

Release Note

Minor : HADOOP-3678 did not remove all the cases of spurious IOExceptions logged by DataNode.

• Assignee: Raghu Angadi Assign to me
• Reporter: Raghu Angadi
• Created: 12/Dec/08 22:29
• Updated: 08/Jul/09 16:43
• Resolved: 29/Jan/09 01:44

Description

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.

Issue Links

• relates to: HADOOP-3678 Avoid spurious "DataXceiver: java.io.IOException: Connection reset by peer" errors in DataNode log