[
https://issues.apache.org/jira/browse/GIRAPH-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434556#comment-13434556
]
Eugene Koontz commented on GIRAPH-212:
--------------------------------------
Updated patch with improved Munge flag usage - removed unused
HADOOP_1_AUTHORIZE flag:
||profile||HADOOP_NON_SECURE||HADOOP_NON_INTERVERSIONED_RPC||HADOOP_NON_JOBCONTEXT_IS_INTERFACE||
|hadoop_non_secure|x|x|x|
|hadoop_facebook |x|x| |
|hadoop_0.20.203 | |x|x|
|hadoop_1.0 | |x|x|
|hadoop_0.23 | | | |
|hadoop_2.0.0 | | | |
|hadoop_trunk | | | |
Passes mvn verify with hadoop_0.20.203 (pom.xml's default), hadoop_1.0,
hadoop_0.23, hadoop_2.0.0, hadoop_trunk.
> 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: Eugene Koontz
> Priority: Critical
> Fix For: 0.2.0
>
> Attachments: core-site.xml, GIRAPH-212.patch, GIRAPH-212.patch,
> GIRAPH-212.patch, GIRAPH-212.patch, 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
