giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-742) Worker task finishSuperstep status reporting the wrong superstep number
Date Wed, 08 Jan 2014 22:12:50 GMT

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

Hudson commented on GIRAPH-742:
-------------------------------

FAILURE: Integrated in Giraph-trunk-Commit #1382 (See [https://builds.apache.org/job/Giraph-trunk-Commit/1382/])
GIRAPH-742: Worker task finishSuperstep status reporting the wrong superstep number (cmuchins
via majakabiljo) (majakabiljo: http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=ca442deeb5c63a8d7bcab796067b712de30e910c)
* giraph-core/src/main/java/org/apache/giraph/worker/BspServiceWorker.java
* CHANGELOG
* giraph-core/src/main/java/org/apache/giraph/worker/BspServiceWorker.java.orig


> Worker task finishSuperstep status reporting the wrong superstep number
> -----------------------------------------------------------------------
>
>                 Key: GIRAPH-742
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-742
>             Project: Giraph
>          Issue Type: Bug
>          Components: bsp
>    Affects Versions: 1.1.0
>            Reporter: Craig Muchinsky
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: GIRAPH-742.patch
>
>
> The logic within BspServiceWorker.finishSuperstep() is incrementing the superstep number
before reporting the finishSuperstep status, thus it reports that all workers are done for
a superstep that hasn't started yet. The call to incrCachedSuperstep() in that method should
be moved down 1 execution line below the call to getContext().setStatus().



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message