[
https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914090#comment-13914090
]
Vinod Kumar Vavilapalli commented on YARN-1577:
-----------------------------------------------
Let's not put in any hacks. Using ApplicationAttemptReport is the right
approach.
Unmanaged AMs are supposed to be used by invoking the Unmanaged-AM tool itself.
We never made the underlying state interaction in the ResourceManager a public
interface.
bq. However, this would not be backwards compatible since it involves changes
to the unmanaged clients. Since I do not see any documentation for the
unmanaged clients, is this acceptable?
It isn't an incompatible change. Like I said above, the AM-RM life-cycle isn't
a publicly supported interface if not used via the unmanaged-AM tool.
Clearly we need documentation stating these things.
> Unmanaged AM is broken because of YARN-1493
> -------------------------------------------
>
> Key: YARN-1577
> URL: https://issues.apache.org/jira/browse/YARN-1577
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.3.0
> Reporter: Jian He
> Assignee: Naren Koneru
> Priority: Blocker
>
> Today unmanaged AM client is waiting for app state to be Accepted to launch
> the AM. This is broken since we changed in YARN-1493 to start the attempt
> after the application is Accepted. We may need to introduce an attempt state
> report that client can rely on to query the attempt state and choose to
> launch the unmanaged AM.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
