giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitay Joffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-391) Zookeeper setup in GraphMapper should check for existence of the jar file
Date Sat, 19 Jan 2013 05:26:13 GMT

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

Nitay Joffe commented on GIRAPH-391:
------------------------------------

Is this still valid? If so can you rebase the patch and we'll take a look, otherwise let's
close this issue.
                
> Zookeeper setup in GraphMapper should check for existence of the jar file
> -------------------------------------------------------------------------
>
>                 Key: GIRAPH-391
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-391
>             Project: Giraph
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: Ravi Prakash
>         Attachments: giraph-391_1.patch, giraph-391.patch
>
>
> Distributed Cache behaviour has changed in Hadoop 0.23. 
> When running on the PageRankBenchmark on a pseudo-distributed setup, GraphMapper.java:303
returns null
> bq. Path[] fileClassPaths = DistributedCache.getLocalCacheArchives(conf);
> Further, context.getJar() returns the location of the job jar in *HDFS* . Obviously this
can't be added to the classpath. If we only checked for the existence of this jar file, it
would follow on to using the findContainingJar() method which returns the right thing.

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

Mime
View raw message