hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2746) [MR-279] [Security] Yarn servers can't communicate with each other with hadoop.security.authorization set to true
Date Fri, 21 Oct 2011 09:42:32 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132556#comment-13132556

Hadoop QA commented on MAPREDUCE-2746:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 18 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1099//console

This message is automatically generated.
> [MR-279] [Security] Yarn servers can't communicate with each other with hadoop.security.authorization
set to true
> -----------------------------------------------------------------------------------------------------------------
>                 Key: MAPREDUCE-2746
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2746
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mrv2, security
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Arun C Murthy
>            Priority: Blocker
>             Fix For: 0.23.0
>         Attachments: MAPREDUCE-2746.patch, MAPREDUCE-2746.patch
> Because of this problem, till now, we've been testing YARN+MR with {{hadoop.security.authorization}}
set to false. We need to register yarn communication protocols in the implementation of the
authorization related PolicyProvider (MapReducePolicyProvider.java).
> [~devaraj] also found this issue independently.

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


View raw message