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

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Blocker
Resolution: Fixed
Affects Version/s: 0.18.2
Fix Version/s: 0.19.1
Component/s: None
Labels:
None
Environment:

Hide

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

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

Hadoop Flags:

Reviewed
Release Note:

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

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

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.