[
https://issues.apache.org/jira/browse/HAMA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579011#comment-13579011
]
Edward J. Yoon commented on HAMA-733:
-------------------------------------
I don't understand OBLSYNC perfectly at the moment, but it seems different with
this concept. It looks like OBLSYNC can be used only when user knows exactly
how messages will be exchanged between N peers. e.g., binary search, sort, ...,
etc. In this case, every message should be sent with its corresponding
superstep number to avoid race condition. If I am wrong, Please correct me. and
Please feel free to suggest your idea.
I'll also take HAMA-643.
> Synchronization without clearing the unconsumed messages in the queues
> ----------------------------------------------------------------------
>
> Key: HAMA-733
> URL: https://issues.apache.org/jira/browse/HAMA-733
> Project: Hama
> Issue Type: Improvement
> Components: bsp core
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.6.1
>
> Attachments: appendSync.txt
>
>
> This function can be useful when broadcast is needed before receiving all
> messages.
> {code}
> /**
> * if true, synchronizes without clearing the unconsumed messages in the
> queues.
> *
> * @throws IOException
> * @throws SyncException
> * @throws InterruptedException
> */
> public void sync(boolean append) throws IOException, SyncException,
> InterruptedException;
> {code}
--
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
