You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Eugene Koontz (JIRA)" <ji...@apache.org> on 2012/10/03 20:42:08 UTC

[jira] [Updated] (GIRAPH-212) Security is busted since GIRAPH-168

     [ https://issues.apache.org/jira/browse/GIRAPH-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Koontz updated GIRAPH-212:
---------------------------------

    Attachment: GIRAPH-212.patch

Updated patch to latest trunk. 

Passes:

{code}
mvn -Phadoop_non_secure clean verify && \
mvn clean verify && \
mvn -Phadoop_1.0 clean verify && \
mvn -Phadoop_2.0.0 clean verify
{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: 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, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira