hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl
Date Tue, 04 Sep 2012 22:37:07 GMT

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

Vinod Kumar Vavilapalli commented on YARN-78:
---------------------------------------------

Ahm, going back on this one. May be it is better to make UnmanagedAMLauncher extend YarnClientImpl
instead of composing it. That way the launcher itself can also be a service that be started/stopped
etc. For example, with the current code/patch, you will have to trap all exceptions in {{run()}}
and make sure that the client connection is closed correctly.

Thoughts?
                
> 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-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

Mime
View raw message