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 "Xuan Gong (JIRA)" <ji...@apache.org> on 2014/06/26 00:56:26 UTC

[jira] [Updated] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to

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

Xuan Gong updated YARN-614:
---------------------------

    Summary: Separate AM failures from hardware failure or YARN error and do not count them to   (was: Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1)

> Separate AM failures from hardware failure or YARN error and do not count them to 
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-614
>                 URL: https://issues.apache.org/jira/browse/YARN-614
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Bikas Saha
>            Assignee: Xuan Gong
>             Fix For: 2.5.0
>
>         Attachments: YARN-614-0.patch, YARN-614-1.patch, YARN-614-2.patch, YARN-614-3.patch, YARN-614-4.patch, YARN-614-5.patch, YARN-614-6.patch, YARN-614.7.patch
>
>
> Attempts can fail due to a large number of user errors and they should not be retried unnecessarily. The only reason YARN should retry an attempt is when the hardware fails or YARN has an error. NM failing, lost NM and NM disk errors are the hardware errors that come to mind.



--
This message was sent by Atlassian JIRA
(v6.2#6252)