hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anubhav Dhoot (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4180) AMLauncher does not retry on failures when talking to NM
Date Fri, 18 Sep 2015 18:17:04 GMT

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

Anubhav Dhoot updated YARN-4180:
    Attachment: YARN-4180.001.patch

reuse the same retry proxy used by AM client for RM client. Also opened YARN-4185 to improve
this retry mechanism

> AMLauncher does not retry on failures when talking to NM 
> ---------------------------------------------------------
>                 Key: YARN-4180
>                 URL: https://issues.apache.org/jira/browse/YARN-4180
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>            Priority: Critical
>         Attachments: YARN-4180.001.patch
> We see issues with RM trying to launch a container while a NM is restarting and we get
exceptions like NMNotReadyException. While YARN-3842 added retry for other clients of NM (AMs
mainly) its not used by AMLauncher in RM causing there intermittent errors to cause job failures.
This can manifest during rolling restart of NMs. 

This message was sent by Atlassian JIRA

View raw message