Return-Path: Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: (qmail 16860 invoked from network); 28 Jul 2010 14:11:39 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Jul 2010 14:11:39 -0000 Received: (qmail 26326 invoked by uid 500); 28 Jul 2010 14:11:38 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 25973 invoked by uid 500); 28 Jul 2010 14:11:35 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 25965 invoked by uid 99); 28 Jul 2010 14:11:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jul 2010 14:11:35 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of msegel@navteq.com designates 204.120.70.37 as permitted sender) Received: from [204.120.70.37] (HELO xmailfargo.navteq.com) (204.120.70.37) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jul 2010 14:11:26 +0000 Received: from fargo-spamfw.navteq.com (navteq-spamfw.navteq.com [10.6.10.131]) by xmailfargo.navteq.com (8.13.6/8.13.6) with ESMTP id o6SDncoQ000544 for ; Wed, 28 Jul 2010 08:49:39 -0500 Received: from imailfargo.navteq.com (localhost [127.0.0.1]) by fargo-spamfw.navteq.com (Spam & Virus Firewall) with ESMTP id 15BB7487FEAC for ; Wed, 28 Jul 2010 09:10:49 -0500 (CDT) Received: from imailfargo.navteq.com (imailfargo.navteq.com [10.6.10.130]) by fargo-spamfw.navteq.com with ESMTP id 9gjKiu3aq7sMS8nE for ; Wed, 28 Jul 2010 09:10:49 -0500 (CDT) Received: from hq-ex-ht01.ad.navteq.com ([10.8.222.51]) by imailfargo.navteq.com (8.13.6/8.13.6) with ESMTP id o6SEAmEH016866 for ; Wed, 28 Jul 2010 09:10:48 -0500 Received: from hq-ex-mb02.ad.navteq.com ([fe80::880d:318e:e860:a8db]) by hq-ex-ht01.ad.navteq.com ([fe80::55a6:5b94:5c00:fe39%12]) with mapi; Wed, 28 Jul 2010 09:10:47 -0500 From: "Segel, Mike" To: "common-dev@hadoop.apache.org" Date: Wed, 28 Jul 2010 09:10:47 -0500 Subject: RE: Starting a job on a hadoop cluster remotly Thread-Topic: Starting a job on a hadoop cluster remotly Thread-Index: AcsuUCFkIqbk+BR6TxeXuhuDAuVO1QADXIHA Message-ID: References: <1EDC794577E2394E9D3D74DFD4D41C210166498C@Mail05.o4b.fn> In-Reply-To: <1EDC794577E2394E9D3D74DFD4D41C210166498C@Mail05.o4b.fn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, Since you didn't get an answer... yes you can. I'm working from memory so I may be a bit fuzzy on the details... Your external app has to be 'cloud aware'. Essentially create a config fi= le for your application that you can read in which lets your app know whe= re the JT and NN are. Then you can use the Tool (?interface/class) implement/extend with your j= ob class and tell it to run... Sorry for being terse... I'm under the gun on getting something out the d= oor. HTH -Mike -----Original Message----- From: Sebastian Ruff (open4business GmbH) [mailto:ruff@open4business.de]=20 Sent: Wednesday, July 28, 2010 7:27 AM To: common-dev@hadoop.apache.org Subject: Starting a job on a hadoop cluster remotly Hey, =20 is it possible to start a job on a hadoop cluster from remote. For example we have a web application which runs on an apache tomcat server. And would like to start a mapreduce job on our cluster, from within the webapp. =20 Is this possible? And if yes, what are the steps to get there? Do I just have to put my namenode and datanode in a core-site.xml in the webapp and call the api? =20 Thanks a lot, =20 Sebastian The information contained in this communication may be CONFIDENTIAL and i= s intended only for the use of the recipient(s) named above. If you are = not the intended recipient, you are hereby notified that any disseminatio= n, distribution, or copying of this communication, or any of its contents= , is strictly prohibited. If you have received this communication in err= or, please notify the sender and delete/destroy the original message and = any copy of it from your computer or paper files.