[HADOOP-14034] Allow ipc layer exceptions to selectively close connections

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.9.0, 3.0.0-alpha4, 2.8.2
• Component/s: ipc
• Target Version/s: 2.8.1
• Hadoop Flags: Reviewed
• Assignee: Daryn Sharp Assign to me
• Reporter: Daryn Sharp
• Created: 27/Jan/17 22:20
• Updated: 08/Jun/17 00:13
• Resolved: 09/Feb/17 17:05

Description

IPC layer exceptions generated in the readers are translated into fatal errors - resulting in connection closure. Ex. RetriableExceptions from call queue pushback.

Always closing the connection degrades performance for all clients since a disconnected client will immediately reconnect on retry. Readers become overwhelmed servicing new connections and re-authentications from bad clients instead of servicing calls from good clients. The call queues run dry.

Exceptions originating in the readers should be able to indicate if the exception is an error or fatal so connections can remain open.

Issue Links

• incorporates: HADOOP-13486 Method invocation in log can be replaced by variable because the variable's toString method contain more info