hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-542) Change the default global AM max-attempts value to be not one
Date Thu, 25 Apr 2013 18:48:16 GMT

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

Bikas Saha commented on YARN-542:

I think that the global default should be one because an app attempt can fail due to a large
number of user level reasons and should not be retried. The system should retry an attempt
upon hardware failure or YARN error and set this default to 1.
> Change the default global AM max-attempts value to be not one
> -------------------------------------------------------------
>                 Key: YARN-542
>                 URL: https://issues.apache.org/jira/browse/YARN-542
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Zhijie Shen
>             Fix For: 2.0.5-beta
>         Attachments: YARN-542.1.patch
> Today, the global AM max-attempts is set to 1 which is a bad choice. AM max-attempts
accounts for both AM level failures as well as container crashes due to localization issue,
lost nodes etc. To account for AM crashes due to problems that are not caused by user code,
mainly lost nodes, we want to give AMs some retires.
> I propose we change it to atleast two. Can change it to 4 to match other retry-configs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message