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 "Anubhav Dhoot (JIRA)" <ji...@apache.org> on 2015/09/18 00:07:05 UTC

[jira] [Commented] (YARN-4180) AMLauncher does not retry on failures when talking to NM

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

Anubhav Dhoot commented on YARN-4180:
-------------------------------------

Propose using retries in the ContainerManagement proxy used by the AMLauncher#getContainerMgrProxy

> 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
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>
> 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
(v6.3.4#6332)