incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <>
Subject [jira] [Commented] (HAMA-376) Refactor BSPMaster and GroomServer to allow rpc methods reuse
Date Mon, 18 Apr 2011 08:40:05 GMT


Edward J. Yoon commented on HAMA-376:

We'll not use the ant build. Please don't edit the build.xml.

Instead, try this patch.

By setting few properties up at HamaTestCase.init(), we can run the bspCluster on eclipse.
The maven build also works well.

  private void init() {
    conf = new HamaConfiguration();
    conf.setStrings("bsp.local.dir", "/tmp/hama-test");
    conf.set("bsp.master.address", "localhost");
    conf.set(Constants.ZOOKEEPER_QUORUM, "localhost");
    conf.set("", "");

And, must we use the examples.jar?

I think, we can simply add some small 'testJob.jar' file to SVN repository for job submission
unit test.

> Refactor BSPMaster and GroomServer to allow rpc methods reuse
> -------------------------------------------------------------
>                 Key: HAMA-376
>                 URL:
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp
>    Affects Versions: 0.3.0
>         Environment: Debian squeeze/sid, java 1.6.0_22, Hama revision 1090950
>            Reporter: ChiaHung Lin
>            Assignee: ChiaHung Lin
>              Labels: patch
>             Fix For: 0.3.0
>         Attachments: HAMA-376.patch, HAMA-376.patch, HAMA-376.patch, HAMA-376.patch
> The current Hama BSPMaster and GroomServer make use of dispatch() and report() function
for communication. But the directives passed in is composite, which is a bit difficult to
customize new directives for future use. The refactored version allows to pass customized
directives by extending Directive class; and the customized directive will be processed with
corresponded handler. Also, directives are put into queue, so the rpc method e.g. dispatch()
do not need to go through the whole method until the execution is finished. 

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message