incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (HAMA-439) Reorganize modules for YARN/MR-NextGen integration
Date Tue, 27 Sep 2011 17:09:46 GMT

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

Thomas Jungblut edited comment on HAMA-439 at 9/27/11 5:09 PM:
---------------------------------------------------------------

Great, I will change your script and your patch then. This way seems to be much cleaner.
I use the branch for indentifying the problems we could possibly have, otherwise I was a bit
too quick again in action. 

{quote}
I wanted to separate the user facing APIs separated from the implementation details completely,
so introduced that to include all the client side tools. In the short term, it may not be
big deal, but I can see potential benefits. We can club them later as we move through this
ticket if we don't realize any such benefit.
{quote}

I see some benefits, too. But I'm not sure about the coupling though. Maybe I can find a clear
trick to decompose the stuff.

{quote}
Yes I recognized that. Didn't know you were on your way to generating patch too, so thought
of unblocking you 
{quote}

That is not a big deal. I'm happy that it is going forward. :)
                
      was (Author: thomas.jungblut):
    Great, I will change your script and your patch then. This way seems to be much cleaner.
I use the branch for indentifying the problems we could possibly have, otherwise I was a bit
too quick again in action. 

{quote}
I wanted to separate the user facing APIs separated from the implementation details completely,
so introduced that to include all the client side tools. In the short term, it may not be
big deal, but I can see potential benefits. We can club them later as we move through this
ticket if we don't realize any such benefit.
{quote}

I see some benefits, too. But I'm not sure about the coupling though. Maybe I can find a clear
trick to decompose the stuff.

{quote}
Yes I recognized that. Didn't know you were on your way to generating patch too, so thought
of unblocking you 
                  
> Reorganize modules for YARN/MR-NextGen integration
> --------------------------------------------------
>
>                 Key: HAMA-439
>                 URL: https://issues.apache.org/jira/browse/HAMA-439
>             Project: Hama
>          Issue Type: Sub-task
>    Affects Versions: 0.3.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Thomas Jungblut
>             Fix For: 0.4.0
>
>         Attachments: HAMA-349-20110927.txt, HAMA-349-move-20110927.sh, HAMA-439.patch
>
>
> I'd like to get started on HamaV2 to work with YARN/MR-nextgen.
> Here's what I think should be the module structure:
>  - *api*: Code from HamaV1 related to APIs that will be moved to this new module. This
will mainly have the BSP APIs: _BSP_, _BSPPeerInterface_ and all the related records like
_BSPMessage_, _BSPMessageBundle etc.
>  - *core*: Current/HamaV1 server code. Will have the current _BSPMaster_/_GroomServer_
infrastructure. We should probably rename it to {{classic-server}} or something similar.
>  - *server*: New Hama server implementation to work with YARN. Will have _BSPApplicationMaster_,
_BSPTask_ and related code.
>  - *client*: Code from HamaV1 related to client that will be moved to this new module.
This will mainly have the client-submission classes/interfaces like _BSPJob_, _BSPJobClient_,
_JobStatus_ etc. It will be configurable to either run with the classic-server implementation
or with YARN.
> There will not be any package changes but only code-moves across modules, so we will
be backwards compatible.
> How does it look? Any thoughts/suggestions?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message