Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9F285D0B5 for ; Thu, 23 Aug 2012 15:43:43 +0000 (UTC) Received: (qmail 77763 invoked by uid 500); 23 Aug 2012 15:43:43 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 77712 invoked by uid 500); 23 Aug 2012 15:43:43 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 77505 invoked by uid 99); 23 Aug 2012 15:43:43 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Aug 2012 15:43:43 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AE62B2C0A51 for ; Thu, 23 Aug 2012 15:43:42 +0000 (UTC) Date: Fri, 24 Aug 2012 02:43:42 +1100 (NCT) From: "Daryn Sharp (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <47896978.5982.1345736622714.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (HADOOP-8225) DistCp fails when invoked by Oozie MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated HADOOP-8225: -------------------------------- Component/s: security Priority: Blocker (was: Major) Target Version/s: 0.23.3, 3.0.0, 2.2.0-alpha Affects Version/s: 3.0.0 2.0.0-alpha Marking as blocker since distcp and other apps that launch jobs can't work under oozie. > DistCp fails when invoked by Oozie > ---------------------------------- > > Key: HADOOP-8225 > URL: https://issues.apache.org/jira/browse/HADOOP-8225 > Project: Hadoop Common > Issue Type: Bug > Components: security > Affects Versions: 0.23.1, 2.0.0-alpha, 3.0.0 > Reporter: Mithun Radhakrishnan > Assignee: Daryn Sharp > Priority: Blocker > Attachments: HADOOP-8225.patch, HADOOP-8225.patch, HADOOP-8225.patch, HADOOP-8225.patch, HADOOP-8225.patch > > > When DistCp is invoked through a proxy-user (e.g. through Oozie), the delegation-token-store isn't picked up by DistCp correctly. One sees failures such as: > ERROR [main] org.apache.hadoop.tools.DistCp: Couldn't complete DistCp > operation: > java.lang.SecurityException: Intercepted System.exit(-999) > at > org.apache.oozie.action.hadoop.LauncherSecurityManager.checkExit(LauncherMapper.java:651) > at java.lang.Runtime.exit(Runtime.java:88) > at java.lang.System.exit(System.java:904) > at org.apache.hadoop.tools.DistCp.main(DistCp.java:357) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:394) > at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54) > at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:399) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:334) > at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:147) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:396) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1177) > at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:142) > Looking over the DistCp code, one sees that HADOOP_TOKEN_FILE_LOCATION isn't being copied to mapreduce.job.credentials.binary, in the job-conf. I'll post a patch for this shortly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira