YARN-3238. Connection timeouts to nodemanagers are retried at multiple

levels. Contributed by Jason Lowe

(cherry picked from commit 92d67ace32)
This commit is contained in:
Xuan 2015-02-21 16:06:12 -08:00
parent 83f779e49a
commit fefeba4ac8
2 changed files with 3 additions and 1 deletions

View File

@ -601,6 +601,9 @@ Release 2.7.0 - UNRELEASED
YARN-3194. RM should handle NMContainerStatuses sent by NM while YARN-3194. RM should handle NMContainerStatuses sent by NM while
registering if NM is Reconnected node (Rohith via jlowe) registering if NM is Reconnected node (Rohith via jlowe)
YARN-3238. Connection timeouts to nodemanagers are retried at
multiple levels (Jason Lowe via xgong)
Release 2.6.0 - 2014-11-18 Release 2.6.0 - 2014-11-18
INCOMPATIBLE CHANGES INCOMPATIBLE CHANGES

View File

@ -72,7 +72,6 @@ public class ServerProxy {
exceptionToPolicyMap.put(ConnectException.class, retryPolicy); exceptionToPolicyMap.put(ConnectException.class, retryPolicy);
exceptionToPolicyMap.put(NoRouteToHostException.class, retryPolicy); exceptionToPolicyMap.put(NoRouteToHostException.class, retryPolicy);
exceptionToPolicyMap.put(UnknownHostException.class, retryPolicy); exceptionToPolicyMap.put(UnknownHostException.class, retryPolicy);
exceptionToPolicyMap.put(ConnectTimeoutException.class, retryPolicy);
exceptionToPolicyMap.put(RetriableException.class, retryPolicy); exceptionToPolicyMap.put(RetriableException.class, retryPolicy);
exceptionToPolicyMap.put(SocketException.class, retryPolicy); exceptionToPolicyMap.put(SocketException.class, retryPolicy);