[
https://issues.apache.org/jira/browse/HAMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104619#comment-13104619
]
Thomas Jungblut commented on HAMA-387:
--------------------------------------
I tested it with my 5 VMs. It is stable for bench example (args: 1048576 200
1000). Great work! :D
But I faced a bug which is going to cause the SSSP example to fail:
{noformat}
2011-09-14 18:12:55,986 INFO org.apache.hama.bsp.TaskRunner:
attempt_201109141809_0001_000001_0 java.lang.ArrayIndexOutOfBoundsException: 1
2011-09-14 18:12:55,986 INFO org.apache.hama.bsp.TaskRunner:
attempt_201109141809_0001_000001_0 at
org.apache.hama.bsp.BSPPeer.getAddress(BSPPeer.java:509)
2011-09-14 18:12:55,986 INFO org.apache.hama.bsp.TaskRunner:
attempt_201109141809_0001_000001_0 at
org.apache.hama.bsp.BSPPeer.send(BSPPeer.java:279)
2011-09-14 18:12:55,986 INFO org.apache.hama.bsp.TaskRunner:
attempt_201109141809_0001_000001_0 at
org.apache.hama.examples.graph.ShortestPaths.sendMessageToNeighbors(ShortestPaths.java:157)
2011-09-14 18:12:55,986 INFO org.apache.hama.bsp.TaskRunner:
attempt_201109141809_0001_000001_0 at
org.apache.hama.examples.graph.ShortestPaths.bsp(ShortestPaths.java:66)
2011-09-14 18:12:55,986 INFO org.apache.hama.bsp.TaskRunner:
attempt_201109141809_0001_000001_0 at
org.apache.hama.bsp.BSPTask.run(BSPTask.java:60)
2011-09-14 18:12:55,986 INFO org.apache.hama.bsp.TaskRunner:
attempt_201109141809_0001_000001_0 at
org.apache.hama.bsp.GroomServer$BSPPeerChild.main(GroomServer.java:940)
{noformat}
ArrayIndexOutOfBoundsException is some serious business.
> Advanced Barrier Synchronization
> --------------------------------
>
> Key: HAMA-387
> URL: https://issues.apache.org/jira/browse/HAMA-387
> Project: Hama
> Issue Type: Improvement
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-387_v02.patch, HAMA-387_v03.patch,
> HAMA-387_v04.patch, new.patch, sleepless.patch, x.PNG, x.patch
>
>
> I think, the lock file must include:
> * the job ID
> * the task ID of the lock file owner
> * the current superstep count
> to check ownership and validation.
> Currently they are named by hostname, but multi-tasks can be run per one
> groomserver in the future.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
