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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/05/29 23:00:22 UTC

[jira] [Resolved] (YARN-3744) ResourceManager should avoid allocating AM to same node repeatedly in case of AM launch failures

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

Vinod Kumar Vavilapalli resolved YARN-3744.
-------------------------------------------
    Resolution: Duplicate

I think this is a dup of YARN-2005. Please reopen if you disagree.

> ResourceManager should avoid allocating AM to same node repeatedly in case of AM launch failures
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3744
>                 URL: https://issues.apache.org/jira/browse/YARN-3744
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Jaideep Dhok
>
> We have seen that if AM launch fails on some node due to configuration or bad disk issue [YARN-3591], quite often it gets reallocated on the same node, causing job failures if the AM attempt limit is reached.
> It would be preferable if the scheduler can try to allocate AM on different nodes for subsequent attempts



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)