[
https://issues.apache.org/jira/browse/HAMA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579027#comment-13579027
]
Suraj Menon commented on HAMA-733:
----------------------------------
You are right. Known message counts or not, oblivious synchronization would
break the current consistency model and the example code written over this
should be aware of it. This is a useful concept where a slight compromise with
accuracy is acceptable for better performance. So this would involve
refactoring the code to use multiple synchronization strategies with Oblivious
sync one of them. The point I was trying to make was that the scope of the
problem is too big to be tackled by adding API calls.
> 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
