[
https://issues.apache.org/jira/browse/YARN-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883018#comment-13883018
]
Bikas Saha commented on YARN-745:
---------------------------------
That was the original plan of action for the unmanaged AM launcher. Its just
specialization of yarnclient. Under a flag yarn client impl should be able to
submit an unmanaged AM. However, running in-process or forking a new process
should also be possible. Running in-process would be easier for debugging.
Launching a separate process works for cases where people want to run their app
in unmanaged mode (eg LAMA AM) Also when one already has an AM in jar then one
could launch it in a process with java opts to enabled debugging instead of
writing code to invoke YARNClient in unmanaged mode inside the 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)
