[YARN-10479] RMProxy should retry on SocketTimeout Exceptions

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10.1, 3.4.0
• Fix Version/s: 3.2.2, 3.4.0, 3.3.1, 2.10.2
• Component/s: yarn
• Assignee: Jim Brennan
• Reporter: Jim Brennan
• Created: 02/Nov/20 16:54
• Updated: 23/May/22 05:35
• Resolved: 05/Nov/20 22:45

Description

During an incident involving a DNS outage, a large number of nodemanagers failed to come back into service because they hit a socket timeout when trying to re-register with the RM.

SocketTimeoutException is not currently one of the exceptions that the RMProxy will retry. Based on this incident, it seems like it should be. We made this change internally about a year ago and it has been running in production since.