[
https://issues.apache.org/jira/browse/YARN-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882551#comment-13882551
]
Wangda Tan commented on YARN-745:
---------------------------------
+1 for this,
My idea is we can move the major functionality of UnmanagedAMLauncher to
YarnClient.submitApplication. 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(), user can directly use AppliationMasterProtocol. It
will be easier for users develop/debug AM. Because AM and client will be placed
in a same process.
Currently UnmanagedAMLauncher will create a separated process for AM, which
will be harder for debugging, etc.
Any thoughts on this?
> 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)
