giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Martella (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-750) When running a job with -libjars option, zookeeper is launched with the wrong jar
Date Wed, 28 Aug 2013 18:34:52 GMT

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

Claudio Martella commented on GIRAPH-750:
-----------------------------------------

i'm afraid i don't understand the logics of the locateZookeeperClasspath that i believe is
legacy code. I don't understand why we would use the files in the distributed cache as potential
classpath for ZK.
In this patch I use the job jar plus the files in the distributed cache as classpath. If you
have an idea, please give me hints. Moreover, trying to use the containingJar of the current
class (GraphTaskManager) as classpath of ZK (first if block) also is obscure to me...

[~aching], maybe you have an idea as i think this is still Yahoo! code?
                
> When running a job with -libjars option, zookeeper is launched with the wrong jar
> ---------------------------------------------------------------------------------
>
>                 Key: GIRAPH-750
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-750
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Claudio Martella
>         Attachments: GIRAPH-750.diff
>
>
> when the job is submitted with a -libjars option, the classpath of the command to start
zookeeper is set wrongly (to the jar passed through -libjars), and zookeeper does not start.
The job fails with clients not connecting to ZK.

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