[
https://issues.apache.org/jira/browse/HAMA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579140#comment-13579140
]
Suraj Menon commented on HAMA-734:
----------------------------------
In HAMA-733 you are breaking your synchronization consistency and would need to
implement a new relaxed synchronization strategy. In this you would implement
getShallowCopy and getDeepCopy in MessageQueue and the framework would keep
reference count to check whether to instantiate a new message queue or not in
the next superstep. Note that repeating this for number of supersteps would get
really costly.
> 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
