[
https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913743#comment-13913743
]
Jian He commented on YARN-1577:
-------------------------------
YARN-1389 is adding support for getting attempt report into
ApplicationClientProtocol, we can take advantage of that to get the attempt
report.
If people use UnmanagedAMLauncher to launch the unmanaged AM,I think the change
should be hidden from user. For the concern of incompatibility, an alternative
solution would be to hack the app state to return the previous state before
ACCEPTED state when queried, until the attempt reaches the LAUNCHED state.
> 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)
