hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay Kumar Thota (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6875) [Herriot] Couple of issues occurred while running the tests in a cluster with security enabled.
Date Thu, 22 Jul 2010 16:37:51 GMT

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

Vinay Kumar Thota commented on HADOOP-6875:

bq. the config key is already defined as in mapreduce project(src/java/org/apache/hadoop/mapreduce/MRJobConfig.java).
But the patch belongs to common project and it doesn't have defined config key.

> [Herriot] Couple of issues occurred while running the tests in a cluster with security
> -----------------------------------------------------------------------------------------------
>                 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, 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.

View raw message