[
https://issues.apache.org/jira/browse/GIRAPH-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401618#comment-13401618
]
Jakob Homan commented on GIRAPH-212:
------------------------------------
Re-produced your setup (our security is configured correctly and our machines
can't connect to the outside internet):
{noformat}
hadoop jar giraph-0.2-SNAPSHOT.jar
org.apache.giraph.benchmark.PageRankBenchmark -libjars $ECP -e 1 -s 3 -v -V 50
-w 1{noformat} Only difference is we have a separate ZK instance. With one
worker, reproduced your result. However, with more than one worker, RPC fails.
It works for w=1 because the worker doesn't need to open any RPC channels to
other workers. Setting n>1 results in:
{noformat}2012-06-26 19:05:32,097 INFO org.apache.hadoop.ipc.Server: IPC Server
listener on 30001: readAndProcess threw exception
org.apache.hadoop.security.AccessControlException: Server is not configured to
do DIGEST authentication.. Count of bytes read: 0
org.apache.hadoop.security.AccessControlException: Server is not configured to
do DIGEST authentication.
at
org.apache.hadoop.ipc.Server$Connection.saslReadAndProcess(Server.java:966)
at
org.apache.hadoop.ipc.Server$Connection.readAndProcess(Server.java:1180)
at org.apache.hadoop.ipc.Server$Listener.doRead(Server.java:537)
at org.apache.hadoop.ipc.Server$Listener$Reader.run(Server.java:344)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662){noformat}
The worker RPC is showing up trying to open a non-secure RPC and the server is
rejecting it....
> 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
