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

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.17.0
• Fix Version/s: 0.17.2
• Hadoop Flags: Reviewed
• Release Note: Avoid spurious exceptions logged at DataNode when clients read from DFS.
• Assignee: Raghu Angadi
• Reporter: Raghu Angadi
• Created: 01/Jul/08 20:43
• Updated: 16/Feb/09 17:00
• Resolved: 18/Jul/08 00:08

Description

When a client reads data using read(), it closes the sockets after it is done. Often it might not read till the end of a block. The datanode on the other side keeps writing data until the client connection is closed or end of the block is reached. If the client does not read till the end of the block, Datanode writes an error message and stack trace to the datanode log. It should not. This is not an error and it just pollutes the log and confuses the user.

Issue Links

• is related to: HADOOP-4862 A spurious IOException log on DataNode is not completely removed