hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1577) Unmanaged AM is broken because of YARN-1493
Date Wed, 05 Feb 2014 16:36:09 GMT

    [ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892281#comment-13892281
] 

Jian He commented on YARN-1577:
-------------------------------

One thing I noticed is that as stated attempt is now started only after the app is accepted
meaning the tokens are also created and populated into secret manager after app is accepted.
client needs to wait until the UMA  attempt reach certain state and then can register.

> 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: Jian He
>            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)

Mime
View raw message