giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-391) Zookeeper setup in GraphMapper should check for existence of the jar file
Date Wed, 23 Jan 2013 04:58:13 GMT


Eli Reisman commented on GIRAPH-391:

having just worked with this code in 479, its still in its "original form." I have not seen
this type of error before myself, and this code is old and has been in use a long time. Doesn't
mean he's wrong though. But it could be his distributed cache was not working? Will the cache
return a null path under normal circumstances rather than throwing an exception or something?

> Zookeeper setup in GraphMapper should check for existence of the jar file
> -------------------------------------------------------------------------
>                 Key: GIRAPH-391
>                 URL:
>             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,
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:

View raw message