giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-309) Message count is wrong
Date Mon, 03 Sep 2012 21:40:07 GMT

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

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

sorry (got cut off!) the JT page lists "Sent Messages" which implies running total for all
iterations (to me at least) but after running other alga's I see its actually reporting a
changing amount that is for each individual superstep, as they occur. They are never tallied
up in the JT page. Perhaps all we need to do is keep a running total, or alternately, mark
that field as "Sent Messages (Current Superstep)" or something?


                
> 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

Mime
View raw message