[
https://issues.apache.org/jira/browse/GIRAPH-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267301#comment-13267301
]
Avery Ching commented on GIRAPH-169:
------------------------------------
Roman, I just tried with hadoop-1.0.2 with your test case:
hadoop jar target/giraph-0.2-SNAPSHOT-jar-with-dependencies.jar
org.apache.giraph.benchmark.PageRankBenchmark -e 1 -s 10 -v -V 1000 -w 1
hadoop jar target/giraph-0.2-SNAPSHOT-jar-with-dependencies.jar
org.apache.giraph.benchmark.PageRankBenchmark -e 1 -s 10 -v -V 1000 -w 2
Both of them ran 2x. One thing I did do was compile against the hadoop-1.02
version.
mvn -Phadoop_1.0 clean package -DskipTests
Can you verify that you compiled against the correct Hadoop profile?
> How to close all child when a job finished?
> -------------------------------------------
>
> Key: GIRAPH-169
> URL: https://issues.apache.org/jira/browse/GIRAPH-169
> Project: Giraph
> Issue Type: Improvement
> Components: mapreduce
> Affects Versions: 0.2.0
> Environment: sles 11 x64,jdk 1.6,hadoop 0.20.205.0,1 Master and 8
> slaves,
> Reporter: Jianfeng Qian
> Priority: Minor
>
> I ran pagerank at hadoop 0.20.205.0. When the job finished,the child in
> slaves didn't quit immediately and sometimes they never quit and I have to
> kill them.
--
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
