Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 1 Feb 2013 01:20:11 +0000 (UTC)
From: "Sandy Ryza (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12630230.1359672557990.226871.1359681611803@arcas>
In-Reply-To: <JIRA.12630230.1359672557990@arcas>
References: <JIRA.12630230.1359672557990@arcas>
Subject: [jira] [Commented] (MAPREDUCE-4970) Child tasks (try to) create
 security audit log files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sandy Ryza commented on MAPREDUCE-4970:
---------------------------------------

I propose creating a task-log4j.properties without the SecurityAuth logger, and passing that instead of the default to the task.  This is what MR2 does, with container-log4j.properties.
                
> Child tasks (try to) create security audit log files
> ----------------------------------------------------
>
>                 Key: MAPREDUCE-4970
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4970
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>
> After HADOOP-8552, MR child tasks will attempt to create security audit log files with their user names.  On an insecure cluster, this has no effect, but on a secure cluster, log4j will try to create log files for tasks with names like SecurityAuth-joeuser.log.

--
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