You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Edward J. Yoon (JIRA)" <ji...@apache.org> on 2011/09/21 04:37:08 UTC
[jira] [Assigned] (HAMA-439) Reorganize modules for YARN/MR-NextGen
integration
[ https://issues.apache.org/jira/browse/HAMA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon reassigned HAMA-439:
-----------------------------------
Assignee: Edward J. Yoon
> 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
> Assignee: Edward J. Yoon
>
> 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