[MAPREDUCE-5616] MR Client-AppMaster RPC max retries on socket timeout is too high.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0, 3.0.0-alpha1
• Fix Version/s: 2.3.0
• Component/s: client
• Hadoop Flags: Reviewed
• Assignee: Chris Nauroth
• Reporter: Chris Nauroth
• Created: 08/Nov/13 18:15
• Updated: 12/May/16 18:22
• Resolved: 14/Nov/13 18:14

Description

MAPREDUCE-3811 introduced a separate config key for overriding the max retries applied to RPC connections from the MapReduce Client to the MapReduce Application Master. This was done to make failover from the AM to the MapReduce History Server faster in the event that the AM completes while the client thinks it's still running. However, the RPC client uses a separate setting for socket timeouts, and this one is not overridden. The default for this is 45 retries with a 20-second timeout on each retry. This means that in environments subject to connection timeout instead of connection refused, the client waits 15 minutes for failover.

Issue Links

• relates to: MAPREDUCE-3811 Make the Client-AM IPC retry count configurable