[
https://issues.apache.org/jira/browse/HAMA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164429#comment-13164429
]
Thomas Jungblut commented on HAMA-443:
--------------------------------------
Yes.
Still for the long run it would be very cool if we can get some kind of
counters that are sychronized across the cluster after a barrier sync.
This will be a lot more convenient than the tag checking of the messages,
because you then just increment an update counter in your code and after the
sync it is guranteed that the counter value is consistent across the cluster.
Or we can add some kind of a method of "syncCounters", which has less overhead
than a normal sync. But that is just an idea for the future.
> SSSP doesn't works with multi-tasks
> -----------------------------------
>
> Key: HAMA-443
> URL: https://issues.apache.org/jira/browse/HAMA-443
> Project: Hama
> Issue Type: Bug
> Components: examples
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-443.patch, HAMA-443_1.patch, HAMA-443_v2.patch,
> HAMA-443_v3.patch, HAMA-443_v4.patch, HAMA-443_v5.patch, mapToList.patch,
> patch.txt, refactor.patch, test.patch
>
>
> {code}
> root@Cnode1:/usr/local/src/hama-trunk# core/bin/hama jar
> examples/target/hama-examples-0.4.0-incubating-SNAPSHOT.jar sssp Klewno xx
> /user/root/edward/sssp-adjacencylist.txt
> Single Source Shortest Path Example:
> <Startvertex name> <optional: output path> <optional: path to own adjacency
> list textfile!>
> Setting default start vertex to "Frankfurt"!
> Setting start vertex to Klewno!
> Using new output folder: xx
> 11/09/26 09:46:24 INFO graph.ShortestPaths: Starting data partitioning...
> 11/09/26 09:47:12 INFO graph.ShortestPaths: Finished!
> 11/09/26 09:47:12 INFO bsp.BSPJobClient: Running job: job_201109260929_0004
> 11/09/26 09:47:15 INFO bsp.BSPJobClient: Current supersteps number: 0
> 11/09/26 09:47:21 INFO bsp.BSPJobClient: Current supersteps number: 1
> 11/09/26 09:47:33 INFO bsp.BSPJobClient: The total number of supersteps: 1
> Job Finished in 21.553 seconds
> -------------------- RESULTS --------------------
> java.lang.NullPointerException
> at
> org.apache.hama.examples.graph.ShortestPathsBase.printOutput(ShortestPathsBase.java:93)
> at
> org.apache.hama.examples.graph.ShortestPaths.main(ShortestPaths.java:239)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:68)
> at org.apache.hadoop.util.ProgramDriver.driver(ProgramDriver.java:139)
> at org.apache.hama.examples.ExampleDriver.main(ExampleDriver.java:37)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hama.util.RunJar.main(RunJar.java:145)
> {code}
--
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
