[ 
https://issues.apache.org/jira/browse/GIRAPH-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452144#comment-13452144
 ] 

Eli Reisman commented on GIRAPH-309:
------------------------------------

Yes it would. I was not aware that the total messages sent was supposed to 
reset each superstep. Either way I have run it using a number of algorithms 
where I have a good idea what the counts should look like relative to input 
data size, and its working great now.

Perhaps I will throw up a newbie JIRA to change the name of the counter to 
reflect that it is a per-superstep count as everyone using Giraph here had 
taken it to be a cumulative count on first glance as well. And including a 
total msg counter might not be a bad thing either. Having the per-superstep 
count has proven really useful, even when I wasn't sure if it was intended or 
not! Thanks again for the fix.

                
> 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

Reply via email to