hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client
Date Tue, 05 Mar 2013 15:53:12 GMT

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

Robert Joseph Evans commented on YARN-378:
------------------------------------------

YARN does not use configuration directly for launching an application.  The RM does not read
the job.xml at all.  Only the AM does.  YARN uses a protocol buffer to do this, SubmitApplicationRequestProto.
Which in turn holds an ApplicationSubmissionContextProto.  You will need to update ApplicationSubmissionContextProto
to include an optional int for the number of retries.  Then have the RM do more or less the
same thing that you suggested.

For the client side you probably want to create a new map/reduce configuration that the MR
client code will use to populate the protocol buffer field.
                
> ApplicationMaster retry times should be set by Client
> -----------------------------------------------------
>
>                 Key: YARN-378
>                 URL: https://issues.apache.org/jira/browse/YARN-378
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: client, resourcemanager
>         Environment: suse
>            Reporter: xieguiming
>            Assignee: Zhijie Shen
>              Labels: usability
>
> We should support that different client or user have different ApplicationMaster retry
times. It also say that "yarn.resourcemanager.am.max-retries" should be set by client. 

--
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

Mime
View raw message