You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/11/23 20:16:10 UTC
[jira] [Updated] (TINKERPOP3-964) Test XXXGraphComputer on a
Hadoop2 cluster (non-pseudocluster).
[ https://issues.apache.org/jira/browse/TINKERPOP3-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko A. Rodriguez updated TINKERPOP3-964:
------------------------------------------
Assignee: (was: Marko A. Rodriguez)
> Test XXXGraphComputer on a Hadoop2 cluster (non-pseudocluster).
> ---------------------------------------------------------------
>
> Key: TINKERPOP3-964
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-964
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: hadoop, test-suite
> Affects Versions: 3.1.0-incubating
> Reporter: Marko A. Rodriguez
> Fix For: 3.1.1-incubating
>
>
> Seems that [~drobin1437] was having troubles with {{GiraphGraphComputer}} on his Hadoop2 cluster, where (crazy enough) it works fine on his Hadoop2 pseudo-cluster. As such, I think we should test both {{SparkGraphComputer}} and {{GiraphGraphComputer}} on real clusters. Moreover, it would be great to test with the 1-billion edge Friendster graph. We had done this before in the {{MX}}-days, but we should make it part of our testing process (even if its manual). Perhaps using AWS to spin up a cluster "easily."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)