Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 A3FA0D7C3 for ; Wed, 11 Jul 2012 14:12:40 +0000 (UTC) Received: (qmail 31980 invoked by uid 500); 11 Jul 2012 14:12:38 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 31412 invoked by uid 500); 11 Jul 2012 14:12:38 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 31315 invoked by uid 99); 11 Jul 2012 14:12:36 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2012 14:12:36 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id C11A014052D for ; Wed, 11 Jul 2012 14:12:36 +0000 (UTC) Date: Wed, 11 Jul 2012 14:12:36 +0000 (UTC) From: "Harsh J (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1990588223.35480.1342015956793.JavaMail.jiratomcat@issues-vm> In-Reply-To: <620343223.28098.1341926083594.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (MAPREDUCE-4421) Remove dependency on deployed MR jars 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/MAPREDUCE-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411544#comment-13411544 ] Harsh J commented on MAPREDUCE-4421: ------------------------------------ Thanks Kihwal and Arun. I guess if its via a central, i.e., a dist-cache, we may lose some heterogenous cluster abilities (different OS versions forming a single cluster, with a chance that one's natives may not work on the other and needs uniquely compiled sets for each). Not much of a worry, and I've hardly seen folks do this in the long run, but might be worth providing a solution for, in the future? > Remove dependency on deployed MR jars > ------------------------------------- > > Key: MAPREDUCE-4421 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4421 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Affects Versions: 2.0.0-alpha > Reporter: Arun C Murthy > Assignee: Arun C Murthy > > Currently MR AM depends on MR jars being deployed on all nodes via implicit dependency on YARN_APPLICATION_CLASSPATH. > We should stop adding mapreduce jars to YARN_APPLICATION_CLASSPATH and, probably, just rely on adding a shaded MR jar along with job.jar to the dist-cache. -- 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