[MAPREDUCE-4954] ShuffleHandler logs excessively when channel closed prematurely by reducer

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.0.3-alpha, 0.23.5
• Assignee: Unassigned
• Reporter: Jason Darrell Lowe
• Created: 22/Jan/13 16:16
• Updated: 22/Jan/13 16:22
• Resolved: 22/Jan/13 16:22

Description

As initially reported in MAPREDUCE-4801, the shuffle protocol allows a reducer to hangup the connection to a nodemanager after receiving the shuffle header. This can introduce a connection reset IOException or a ClosedChannelException on the nodemanager. Logging these is not very interesting, and adds a lot of data to the NM log.

MAPREDUCE-4801 missed some places where these exceptions can occur, will post sample exceptions below for reference.