hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HAMA-461) Extract a Message Service from BSPPeer
Date Mon, 07 Nov 2011 07:57:51 GMT

     [ https://issues.apache.org/jira/browse/HAMA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thomas Jungblut updated HAMA-461:

    Attachment: HAMA-461_v2.patch

Should be fixed now, I forgot to call init and therefore the configuration was null.
> Extract a Message Service from BSPPeer
> --------------------------------------
>                 Key: HAMA-461
>                 URL: https://issues.apache.org/jira/browse/HAMA-461
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>             Fix For: 0.4.0
>         Attachments: HAMA-461_v1.patch, HAMA-461_v2.patch
> There's a problem, that we have more synchronized Collections than we need. localQueueForNextIteration
(or similar name) is the only one which needs to be thread safe. At least only the put method
could be synchronized, because reads does not need to be threadsafe.
> So we should refactor our messaging system from the peer itself. 
> A hint in architecture could give us HAMA-457.
> We have to add a factory which let's the user choice their protocol.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message