hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Brennan (Jira)" <j...@apache.org>
Subject [jira] [Commented] (YARN-10479) RMProxy should retry on SocketTimeout Exceptions
Date Thu, 05 Nov 2020 15:29:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-10479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226770#comment-17226770

Jim Brennan commented on YARN-10479:

All of the failed unit tests also fail in trunk, due to the change made in [HADOOP-17306].
[~epayne] can you please review this?

> RMProxy should retry on SocketTimeout Exceptions
> ------------------------------------------------
>                 Key: YARN-10479
>                 URL: https://issues.apache.org/jira/browse/YARN-10479
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: yarn
>    Affects Versions: 2.10.1, 3.4.1
>            Reporter: Jim Brennan
>            Assignee: Jim Brennan
>            Priority: Major
>         Attachments: YARN-10479.001.patch, YARN-10479.002.patch, YARN-10479.003.patch
> 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.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message