[
https://issues.apache.org/jira/browse/HAMA-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222326#comment-13222326
]
ChiaHung Lin commented on HAMA-515:
-----------------------------------
Does that mean each bsp tasks do not want to call sync() but still want to
access other bsp tasks' updated superstep count? If it is, each bsp task can
create a znode pointing to /counter/job_id/superstep/task_id, then placing a
watch under /counter/job_id, so once a task enters a new superstep (e.g.
superstep 1 to superstep 2), other bsp tasks will get notified.
> Counter should be synchronized by sync()
> ----------------------------------------
>
> Key: HAMA-515
> URL: https://issues.apache.org/jira/browse/HAMA-515
> Project: Hama
> Issue Type: New Feature
> Affects Versions: 0.4.0
> Reporter: Thomas Jungblut
> Priority: Minor
> Fix For: 0.5.0
>
>
> We should synchronize the counters in all tasks after a sync() call.
> Then someone can use it for flow control. E.G. graph related algorithms, to
> get the number of globally updated vertices.
> Two options to solve this:
> - Sync the whole stuff over RPC from the BSPMaster
> - Use Zookeeper for counter handling
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
