You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Masatake Iwasaki (Jira)" <ji...@apache.org> on 2022/05/23 05:35:00 UTC

[jira] [Updated] (YARN-10479) RMProxy should retry on SocketTimeout Exceptions

     [ https://issues.apache.org/jira/browse/YARN-10479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Masatake Iwasaki updated YARN-10479:
------------------------------------
    Fix Version/s: 3.2.2
                       (was: 3.2.3)

> 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.0
>            Reporter: Jim Brennan
>            Assignee: Jim Brennan
>            Priority: Major
>             Fix For: 3.2.2, 3.4.0, 3.3.1
>
>         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
(v8.20.7#820007)

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