Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Fri, 31 Aug 2012 02:51:07 +1100 (NCT)
From: "Eli Reisman (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <1943755130.16940.1346341867681.JavaMail.jiratomcat@arcas>
In-Reply-To: <203226295.14536.1346284147951.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (GIRAPH-318) New Iterator in LocalityInfoSorter
 is not working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eli Reisman commented on GIRAPH-318:
------------------------------------

Dude. I'M responsible. Sorry. I broke Giraph and it wasn't even while figuring out SVN!

As mentioned in 301 thread, I will do a nice refactor on this bit of the code to encapsulate the input split list fully in GIRAPH-307 as well.

Thanks again!

                
> New Iterator in LocalityInfoSorter is not working
> -------------------------------------------------
>
>                 Key: GIRAPH-318
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-318
>             Project: Giraph
>          Issue Type: Bug
>          Components: graph
>    Affects Versions: 0.2.0
>            Reporter: Eli Reisman
>            Assignee: Eli Reisman
>             Fix For: 0.2.0
>
>         Attachments: GIRAPH-318-1.patch
>
>
> Although I had tested GIRAPH-301-7 extensively on 2 clusters, I did a quick refactor of an Iterator for 301-8 which got committed today. It passed mvn verify and I did not have time to re-run on a cluster yet. When I finally ran it on the cluster just now, there was occasionally an error on certain worker nodes. I will post a fix ASAP but I'm pretty sure for the moment, trunk will fail in input superstep a lot of the time. Fixing now...

--
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