hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl
Date Wed, 05 Sep 2012 19:17:07 GMT

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

Bikas Saha commented on YARN-78:

I have updated the patch to now call stop() and existing test now works. Implementing Service
is a good suggestion but I am holding back on that. Service interface implies existence of
certain service states which AMLauncher is not satisfying. Also, there are a number of other
interface functions like register etc which dont apply to AMLauncher. Going forward if this
evolves from being an executable to a library that other apps build on, then it will be useful
to implement the full fledged service interface like you suggest. Let me know if this sounds
good to you.
> Change UnmanagedAMLauncher to use YarnClientImpl
> ------------------------------------------------
>                 Key: YARN-78
>                 URL: https://issues.apache.org/jira/browse/YARN-78
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.0-alpha, 2.2.0-alpha
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: YARN-78.1.patch, YARN-78.2.patch
> YARN-29 added a common client impl to talk to the RM. Use that in the UnmanagedAMLauncher.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message