incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ChiaHung Lin (JIRA)" <>
Subject [jira] [Commented] (HAMA-376) Refactor BSPMaster and GroomServer to allow rpc methods reuse
Date Wed, 13 Apr 2011 07:49:05 GMT


ChiaHung Lin commented on HAMA-376:

I will look into the miniBSPCluster issue in Eclipse. 

With other examples e.g. PiEstimator will also cause the NullPointerException at GroomServer,
which stems from unabling to unjar the localized file. Basically it looks like at the client
side, the class loader retrieved (sun.misc.Launcher$AppClassLoader) by e.g. PiEstimator is
changed and different from what is set (Thread.currentThread().setContextClassLoader(
in RunJar. 

Sicne the missing jar is not the issue caused by refactored code, a temporary solution can
be done by simply copying example jar from the build folder to hama home.  

> 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
> 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