You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Eli Reisman (JIRA)" <ji...@apache.org> on 2012/08/30 02:28:07 UTC
[jira] [Updated] (GIRAPH-318) New Iterator in LocalityInfoSorter is
not working
[ https://issues.apache.org/jira/browse/GIRAPH-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Reisman updated GIRAPH-318:
-------------------------------
Attachment: GIRAPH-318-1.patch
Sorry everyone. This fixes the mess-up in my iterator that got past maven this morning, just ran it on the cluster, we're all good now once this is in.
> 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