You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org> on 2011/10/21 10:52:32 UTC
[jira] [Commented] (MAPREDUCE-2746) [MR-279] [Security] Yarn
servers can't communicate with each other with
hadoop.security.authorization set to true
[ https://issues.apache.org/jira/browse/MAPREDUCE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132522#comment-13132522 ]
Hadoop QA commented on MAPREDUCE-2746:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12500163/MAPREDUCE-2746.patch
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/1098//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
>
>
> 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