incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HAMA-247) Discuss / Refactor HamaMaster and GroomServer
Date Thu, 22 Apr 2010 12:12:50 GMT

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

Hyunsik Choi commented on HAMA-247:
-----------------------------------

Hudson results in "no new or modified tests" and 1 new findbugs warning.
We are  working for test units for BSPMaster and GroomServer in HAMA-252.
Thus, I'll attach an improved patch to only fix findbugs warnings.

But, now I cannot access the recent build's findbugs warnings ( http://hudson.zones.apache.org/hudson/job/Hama-Patch/235/findbugsResult/
). So, I'll work with the previous build's findbugs warnings ( http://hudson.zones.apache.org/hudson/job/Hama-Patch/234/findbugsResult/
).

Thank you :)

> Discuss / Refactor HamaMaster and GroomServer
> ---------------------------------------------
>
>                 Key: HAMA-247
>                 URL: https://issues.apache.org/jira/browse/HAMA-247
>             Project: Hama
>          Issue Type: Sub-task
>          Components: bsp
>    Affects Versions: 0.2.0
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.2.0
>
>         Attachments: HAMA-247.patch, HAMA-247_2.patch, HAMA-247_3.patch, HAMA-247_4.patch
>
>
> BSP package needs bsp master daemon and bsp slave daemon. We intended HamaMaster and
GroomServer to be bsp master and bsp slave daemon respectively. But, they are now located
in the wrong package. GroomServer is in org.apache.hama.graph ,and HamaMaster is in org.apache.hama.
> Thus, I propose as follows:
>  1) GroomServer should be moved to org.apache.hama.bsp.
>  2) HamaMaster should be moved to org.apache.hama.bsp.
>  3) HamaMaster should be renamed to BSPMaster.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message