giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koontz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-212) Security is busted since GIRAPH-168
Date Mon, 25 Jun 2012 21:16:43 GMT

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

Eugene Koontz commented on GIRAPH-212:
--------------------------------------

I built giraph with:

{code}
mvn -DskipTests -Phadoop_1.0 clean package
{code}

I edited hadoop-env.sh like this:
{code}
# Extra Java CLASSPATH elements.  Optional.
export HADOOP_CLASSPATH=$HOME/.m2/repository/com/google/guava/guava/r09/guava-r09.jar:$HOME/.m2/repository/commons-io/commons-io/1.\
3.2/commons-io-1.3.2.jar:$HOME/.m2/repository/org/apache/zookeeper/zookeeper/3.3.3/zookeeper-3.3.3.jar:$HOME/.m2/repository/org/jso\
n/json/20090211/json-20090211.jar:$HOME/.m2/repository/net/iharder/base64/2.3.8/base64-2.3.8.jar
{code}

Then I ran the job with: (from the directory $HOME/hadoop/build/hadoop-1.0.3-SNAPSHOT)
{code}
bin/hadoop jar ~/giraph/target/munged/giraph-0.2-SNAPSHOT.jar org.apache.giraph.\
benchmark.PageRankBenchmark -e 1 -s 3 -v -V 50 -w 1
{code}

                
> Security is busted since GIRAPH-168
> -----------------------------------
>
>                 Key: GIRAPH-212
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-212
>             Project: Giraph
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.2.0
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>            Priority: Critical
>             Fix For: 0.2.0
>
>         Attachments: core-site.xml, hdfs-site.xml, mapred-site.xml
>
>
> As reported on the mailing list and verified here on our clusters, something's gone screwy
with Giraph jobs on secure hadoop.  I reverted back before GIRAPH-168 and this goes away,
although I've not found out what it is yet (and may not be 168).  
> RPC clients are trying to open connections with the wrong configuration relative to the
servers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message