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

Posted to yarn-dev@hadoop.apache.org by "Eric Payne (JIRA)" <ji...@apache.org> on 2015/10/02 15:23:27 UTC

[jira] [Resolved] (YARN-4217) Failed AM attempt retries on same failed host

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

Eric Payne resolved YARN-4217.
------------------------------
    Resolution: Duplicate

bq. Eric Payne - is this a duplicate of YARN-2005?
[~vvasudev], yes it is. I did do a search, but I missed that one. Thanks a lot!

> Failed AM attempt retries on same failed host
> ---------------------------------------------
>
>                 Key: YARN-4217
>                 URL: https://issues.apache.org/jira/browse/YARN-4217
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: applications
>    Affects Versions: 2.7.1
>            Reporter: Eric Payne
>
> This happens when the cluster is maxed out. One node is going bad, so everything that happens on it fails, so the bad node is never busy. Since the cluster is maxed out, when the RM looks for a node with available resources, it will always find the almost bad one because nothing can run on it so it has available resources.



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