[
https://issues.apache.org/jira/browse/GIRAPH-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447415#comment-13447415
]
Eli Reisman commented on GIRAPH-309:
------------------------------------
I see what happening now. The algo I was running sends the same # of messages
every superstep, it looked frozen at superstep 0. Running other algorithms, I
now see the Hadoop JobTracker detail page says "
> Message count is wrong
> ----------------------
>
> Key: GIRAPH-309
> URL: https://issues.apache.org/jira/browse/GIRAPH-309
> Project: Giraph
> Issue Type: Bug
> Reporter: Avery Ching
> Assignee: Avery Ching
> Priority: Minor
> Attachments: GIRAPH-309.patch
>
>
> Currently, the message count is multiplied by the partitions, which is
> incorrect as it is a total message count for the entire worker. This affects
> the Hadoop counter displayed on the job status page.
> Old incorrect value
> 2012-08-16 00:45:12,307 INFO org.apache.giraph.graph.BspServiceMaster:
> aggregateWorkerStats: Aggregation found
> (vtx=10000000,finVtx=0,edges=100000000,msgCount=599165250,haltComputation=false)
> on superstep = 3
> Fixed value
> 2012-08-20 16:47:11,559 INFO org.apache.giraph.graph.BspServiceMaster:
> aggregateWorkerStats: Aggregation found
> (vtx=10000000,finVtx=0,edges=100000000,msgCount=100000000,haltComputation=false)
> on superstep = 3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
