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 "Iyappan Srinivasan (JIRA)" <ji...@apache.org> on 2010/07/06 05:44:50 UTC
[jira] Commented: (MAPREDUCE-1913) [Herriot] Couple of issues
occurred while running the tests in a cluster with security enabled.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885406#action_12885406 ]
Iyappan Srinivasan commented on MAPREDUCE-1913:
-----------------------------------------------
+ if (props.get(MAPRED_DELEGATION_TOKEN) == null) {
+ initConf.setBoolean(MAPRED_DELEGATION_TOKEN, false);
+ }
- I think it should be, if the delegation token exists, then it should be set to false.
So, should not it be if (props.get(MAPRED_DELEGATION_TOKEN) != null) {
> [Herriot] Couple of issues occurred while running the tests in a cluster with security enabled.
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1913
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1913
> Project: Hadoop Map/Reduce
> 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.