hama-dev 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] (HAMA-439) Reorganize modules for YARN/MR-NextGen integration
Date Mon, 19 Sep 2011 04:15:08 GMT

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

Vinod Kumar Vavilapalli commented on HAMA-439:

bq. [..] having too many modules in the project is not good I think.
Agreed in general, but this is the minimum set that will help us work with both the server

bq. Are this going to be changed in branch first?
Thought about this. The good thing with doing it in a branch is that it will be isolated.
Bbut the real bad thing is the amount of effort to keep the branch in sync with trunk and
finally when you want to merge into trunk. I am tending to do it on trunk. I understand the
instability it causes, will try everything to make it as smooth as possible. But with your
help, I think we can pull it off without much havoc.

Thanks all, let's get this done!

> Reorganize modules for YARN/MR-NextGen integration
> --------------------------------------------------
>                 Key: HAMA-439
>                 URL: https://issues.apache.org/jira/browse/HAMA-439
>             Project: Hama
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message