Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Date: Fri, 17 Jun 2011 16:00:48 +0000 (UTC)
From: "Thomas Jungblut (JIRA)" <jira@apache.org>
To: hama-dev@incubator.apache.org
Message-ID: 
 <601992832.15335.1308326448180.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1581197259.15318.1308326327535.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HAMA-404) LocalBSPRunner returns wrong superstep
 numbers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Jungblut updated HAMA-404:
---------------------------------

    Status: Patch Available  (was: Open)

> LocalBSPRunner returns wrong superstep numbers
> ----------------------------------------------
>
>                 Key: HAMA-404
>                 URL: https://issues.apache.org/jira/browse/HAMA-404
>             Project: Hama
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>            Priority: Critical
>             Fix For: 0.3.0
>
>         Attachments: HAMA-404_v00.patch
>
>
> Superstep is a threadlocal variable in the LocalGroom, so each thread is resposible for itself to increment the superstep after calling sync. 
> In the old logic it was a non-local variable which where just the first thread should increment it.
> Remove the "only first thread updates" logic and let each thread increment the superstep.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira