Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2EF26F950 for ; Mon, 29 Apr 2013 18:16:49 +0000 (UTC) Received: (qmail 15564 invoked by uid 500); 29 Apr 2013 18:16:43 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 15462 invoked by uid 500); 29 Apr 2013 18:16:43 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 15455 invoked by uid 99); 29 Apr 2013 18:16:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2013 18:16:43 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.210.174 as permitted sender) Received: from [209.85.210.174] (HELO mail-ia0-f174.google.com) (209.85.210.174) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2013 18:16:36 +0000 Received: by mail-ia0-f174.google.com with SMTP id h23so5725520iae.19 for ; Mon, 29 Apr 2013 11:16:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=vMQSCI6kWmDRHv0/g1m1LJbSJefhJ9hwPrQD75z9Jzc=; b=UI3mhZKuq4Y9wd1+6hZ5YwX7c4ckI84YCwc64wajfRflKGnIIJhRk8B0nlqR0bYUdh Ifl4HFl+M8b6u0gfT4LdhdI7ojHEsU97uqnueaCBPMDA1MSbRZlxUKzYQdffYu1ZM7MW TN7AMtvAta25HW69v2+fhcs94yNxfDeF2b2V61a0V5TrnDrvnnDha+d3byclmG3h07pS ebkhapvIRD5G4wEo8tDiwzo1UBpEwJRIVndkk2vKzeBrT3AHa4jsdbq6EnUmV2z4R1TN 6UWyNpQE0VJ89/m8sup35CW9bQa4Mp6JbsntT/BQNN1yKRJjqUbjsMbTKYpxWI6UNAvt dIMw== X-Received: by 10.50.134.196 with SMTP id pm4mr8154423igb.93.1367259376051; Mon, 29 Apr 2013 11:16:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.74.162 with HTTP; Mon, 29 Apr 2013 11:15:52 -0700 (PDT) In-Reply-To: <4bd2eeb2.5e5c7e.13e4824c75d.Webtop.48@charter.net> References: <4bd2eeb2.5e5c7e.13e4824c75d.Webtop.48@charter.net> From: Harsh J Date: Mon, 29 Apr 2013 23:45:52 +0530 Message-ID: Subject: Re: M/R job to a cluster? To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmxyMldp5cuSP9vZDuWLQZJO8TnWPbH0RjHl6LxFkzLgpRvgyqn0lCr6H3tm8YNTJRu+mRx X-Virus-Checked: Checked by ClamAV on apache.org To validate if your jobs are running locally, look for the classname "LocalJobRunner" in the runtime output. Configs are sourced either from the classpath (if a dir or jar on the classpath has the XMLs at their root, they're read), or via the code (conf.set("mapred.job.tracker", "foo:349");) or also via -D parameters if you use Tool. The tool + classpath way is usually the best thing to do, for flexibility. On Sat, Apr 27, 2013 at 2:29 AM, wrote: > I suspect that my MapReduce job is being run locally. I don't have any > evidence but I am not sure how the specifics of my configuration are > communicated to the Java code that I write. Based on the text that I have > read online basically I start with code like: > > JobClient client = new JobClient(); > JobConf conf - new JobConf(WordCount.class); > . . . . . > > Where do I communicate the configuration information so that the M/R job > runs on the cluster and not locally? Or is the configuration location > "magically determined"? > > Thank you. -- Harsh J