Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <16870534.526631279833230701.JavaMail.jira@thor>
Date: Thu, 22 Jul 2010 17:13:50 -0400 (EDT)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6875) [Herriot] Couple of issues occurred
 while running the tests in a cluster with security enabled.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Boudnik commented on HADOOP-6875:
--------------------------------------------

Basically, if you need to have this kind of properties for MR - it should go into concrete implementation of a cluster. I believe this is MRCLuster in this case.

> [Herriot] Couple of issues occurred while running the tests in a cluster with security enabled.
> -----------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6875
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6875
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test
>            Reporter: Vinay Kumar Thota
>            Assignee: Vinay Kumar Thota
>         Attachments: 1913-ydist-security.patch, HADOOP-6875.patch, MAPREDUCE-1913.patch
>
>
> 1. New configuration directory is not cleaning up after resetting to default configuration directory in a pushconfig functionality. Because of this reason, it's giving  permission denied problem for a folder, if  other user tried running the tests in the same cluster with pushconfig functionality. I could see this issue while running the tests on a cluster with security enabled and different user.
> I have added the functionality for above issue and attaching the patch
> 2.  Throwing IOException and it says token is expired while running  the tests. I could see this issue in a secure cluster.
> This issue has been resolved by setting the following attribute in the configuration. 
> mapreduce.job.complete.cancel.delegation.tokens=false
>  
> adding/updating this attribute in the push configuration functionality while creating the new configuration.

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