giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alessandro Presta (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-259) TestBspBasic.testBspPageRank is broken
Date Wed, 01 Aug 2012 15:39:02 GMT


Alessandro Presta commented on GIRAPH-259:

Is there any particular reason why MasterCompute#compute() is executed before anything else?
It seems to me that we would be more loyal to the BSP model if we didn't enforce this: MasterCompute
is just a special vertex, executed during the superstep, whose vote to halt wins over everyone
You still use it as the logical place where serial, graph-wide computations are done (for
example, checking the global value of an aggregator as a termination condition), but you don't
rely on the contract that it will be run at any specific time relative to normal vertices.

Especially since we are going to offer auto-resetting aggregators, it makes sense for MasterCompute
to be a normal aggregator user, so collecting aggregators and running compute() are two orthogonal

@Avery: regarding those two failures, please see GIRAPH-276
> TestBspBasic.testBspPageRank is broken
> --------------------------------------
>                 Key: GIRAPH-259
>                 URL:
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Maja Kabiljo
>            Assignee: Maja Kabiljo
>         Attachments: GIRAPH-259-1.patch, GIRAPH-259-2.patch, GIRAPH-259-3.patch
> Test crashes on line 152 in class SimplePageRankVertex in distributed mode.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message