hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-734) Hama Message Manager should be able to delegate the ownership of internal message queue on request for future superstep
Date Fri, 15 Feb 2013 13:29:12 GMT

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

Edward J. Yoon commented on HAMA-734:
-------------------------------------

I admit it's not in the standard BSP model.
 
However, if there are unconsumed messages in current superstep and user want to send them
to next superstep, then user need to poll messages from the queue and send to local queue
again using send() method.

{code}
// unnecassary at this time so send to next step
while((msg = peer.getCurrentMessage()) != null) {
   peer.send(myself, msg);
}

sync();
{code}

Above code can be simplified to one line.

{code}
sync(true/false);
{code}

Are you suggest syncAndPersist() instead of sync(boolean parameter)?

                
> Hama Message Manager should be able to delegate the ownership of internal message queue
on request for future superstep
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HAMA-734
>                 URL: https://issues.apache.org/jira/browse/HAMA-734
>             Project: Hama
>          Issue Type: Improvement
>            Reporter: Suraj Menon
>
> Get the ownership of the messagequeue, to improve performance in scenarios when a certain
set of messages in the queue is to be used in a future superstep than the current one. With
this feature, the message queue could be stored for future without having to read them in
the current superstep. The framework would initialize and create a new message queue internally.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message