hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1481) Move internal services logic from AdminService to ResourceManager
Date Fri, 27 Dec 2013 08:54:51 GMT

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

Hadoop QA commented on YARN-1481:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2737//console

This message is automatically generated.

> Move internal services logic from AdminService to ResourceManager
> -----------------------------------------------------------------
>                 Key: YARN-1481
>                 URL: https://issues.apache.org/jira/browse/YARN-1481
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>             Fix For: 2.4.0
>         Attachments: YARN-1481-20131207.txt, YARN-1481-20131209.txt, yarn-1481-addendum.patch
> This is something I found while reviewing YARN-1318, but didn't halt that patch as many
cycles went there already. Some top level issues
>  - Not easy to follow RM's service life cycle
>     -- RM adds only AdminService as its service directly.
>     -- Other services are added to RM when AdminService's init calls RM.activeServices.init()
>  - Overall, AdminService shouldn't encompass all of RM's HA state management. It was
originally supposed to be the implementation of just the RPC server.

This message was sent by Atlassian JIRA

View raw message