[
https://issues.apache.org/jira/browse/HAMA-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215717#comment-13215717
]
Thomas Jungblut commented on HAMA-409:
--------------------------------------
I believe it is because of the updated condition.
In each task you are going through a part of the graph and check if they send
some messages, if no message is sent, you leave the loop.
I guess this causes a lock in the barrier sync, because not all tasks are
reaching it then.
We had similar problems with SSSP and Pagerank in the beginning ;)
We could use counters to check if vertices have been updated globally
(HAMA-515). Or we have to manage this be messaging like in SSSP we had before.
> Add Pregel-like API
> -------------------
>
> Key: HAMA-409
> URL: https://issues.apache.org/jira/browse/HAMA-409
> Project: Hama
> Issue Type: New Feature
> Components: bsp, examples
> Affects Versions: 0.4.0
> Reporter: Thomas Jungblut
> Assignee: Edward J. Yoon
> Labels: graph
> Fix For: 0.5.0
>
> Attachments: HAMA-409_v01.patch, HAMA-409_v02.patch,
> HAMA-409_v03.patch, HAMA-409_v04.patch, HAMA-409_v05.patch, InlinkCount.java,
> hama-graph.zip, pregel_v01.patch, pregel_v02.patch, pregel_v03.patch, test.txt
>
>
> According to what we've discussed on the mailing list, we should add a
> Pregel-like API.
--
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
