Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <7046965.396511285383933483.JavaMail.jira@thor>
Date: Fri, 24 Sep 2010 23:05:33 -0400 (EDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6951) Distinct minicluster services (e.g.
 NN and JT) overwrite each other's service policies
In-Reply-To: <3990308.158511284404253537.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914746#action_12914746 ] 

Hudson commented on HADOOP-6951:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #379 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/379/])
    Reverting commit 1001067 while related HDFS and MR JIRAs are tested (HADOOP-6951).


> Distinct minicluster services (e.g. NN and JT) overwrite each other's service policies
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6951
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6951
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>             Fix For: 0.22.0
>
>         Attachments: hadoop-6951.1.txt, hadoop-6951.2.txt, hadoop-6951.txt.0
>
>
> Because the protocol -> ACL mapping in ServiceAuthorizationManager is static, services which are run in the same JVM have the potential to clobber the other's service authorization ACLs whenever ServiceAuthorizationManager.refresh() is called. This causes authorization failures if one tries to launch a 2NN connected to a minicluster with hadoop.security.authorization enabled. Seems like each service should have its own instance of a ServiceAuthorizationManager, instead of using static methods.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.