You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@giraph.apache.org by "Craig Muchinsky (JIRA)" <ji...@apache.org> on 2013/08/21 03:53:51 UTC

[jira] [Updated] (GIRAPH-742) Worker task finishSuperstep status reporting the wrong superstep number

     [ https://issues.apache.org/jira/browse/GIRAPH-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Muchinsky updated GIRAPH-742:
-----------------------------------

    Attachment: GIRAPH-742.patch
    
> 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
>         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 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