hama-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon" <edwardy...@apache.org>
Subject Re: communication
Date Tue, 15 Feb 2011 00:37:42 GMT
You can understand it as a barrier count. After all peers have entered
the barrier using sync() method, the system proceeds to the next

And, even if queues are empty, the bsp job won't stop until each
processes terminated. In SerializePrinting example case, the program
will be finished after the for loop is done and the count of
supersteps is same with a number of peers.


On Mon, Feb 14, 2011 at 11:29 PM, PaweĊ‚ Brach <braszek@gmail.com> wrote:
> Thanks for quick bugfix. Could you provide me an example code, where you
> control number of supersteps by sending messages to itself ?
> I'm really confused looking at SerializePrinting example provided with Hama.
> There is no send message and there are 3 supersteps.
> It looks like the number of supersteps in controlled by number of loop
> iterations in the bsp() method.
> What's more, in the javadoc there is info about sync method:
> "Sends all the messages in the outgoing message queues to the corresponding
> remote peers."
> So what is the reason to call sync() in the SerializePrinting example
> (outgoing queue is empty).
> Thanks,
> Pawel
> 2011/2/14 Edward J. Yoon <edwardyoon@apache.org>
>> Oh, thanks for nice report!
>> At this time, it looks like impossible to send one more messages on to
>> same server in bsp() method. It's a bug. I'll fix it now.
>> Pls, update your TRUNK.

Best Regards, Edward J. Yoon

View raw message