[
https://issues.apache.org/jira/browse/YARN-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911163#comment-13911163
]
Wangda Tan commented on YARN-745:
---------------------------------
I think it's still backwards compatible, in past, user has two ways to submit a
unmanaged AM,
1) Submit by UnmanagedAMLauncher
2) Use YarnClient, first get a new app id, then submit app
As I commented,
{quote}
When an application is marked unmanaged in ApplicationSubmissionContext, user
doesn't need set applicationId field in ApplicationSubmissionContext, and
submitApplication() will 1) createApplication 2) wait for application accepted
by RM 3) handle AM tokens, etc.
After submitApplication()
{quote}
It's more like an extend to existed API, if we don't remove the
UnmanagedAMLauncher (just leverage its code in yarn client), users can still
use the previous two methods to submit an unmanaged AM.
> Move UnmanagedAMLauncher to yarn client package
> -----------------------------------------------
>
> Key: YARN-745
> URL: https://issues.apache.org/jira/browse/YARN-745
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Fix For: 2.4.0
>
>
> Its currently sitting in yarn applications project which sounds wrong. client
> project sounds better since it contains the utilities/libraries that clients
> use to write and debug yarn applications.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
