hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naren Koneru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1577) Unmanaged AM is broken because of YARN-1493
Date Fri, 28 Feb 2014 00:06:22 GMT

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

Naren Koneru commented on YARN-1577:
------------------------------------

I see that a patch has been submitted today for YARN-1389. I will look into this once that
issue is resolved since we are gonna make use of the APIs there (getApplicationAttemptReport)
to fi the UnManagedAMLauncher, etc

> 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)

Mime
View raw message