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 AE731FFFD for ; Tue, 9 Apr 2013 03:47:45 +0000 (UTC) Received: (qmail 89882 invoked by uid 500); 9 Apr 2013 03:47:40 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 89612 invoked by uid 500); 9 Apr 2013 03:47:40 -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 89588 invoked by uid 99); 9 Apr 2013 03:47:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 03:47:39 +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 (athena.apache.org: domain of harsh@cloudera.com designates 209.85.210.180 as permitted sender) Received: from [209.85.210.180] (HELO mail-ia0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 03:47:30 +0000 Received: by mail-ia0-f180.google.com with SMTP id l29so581999iag.11 for ; Mon, 08 Apr 2013 20:47:10 -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=hTL74KTN1PlXwYdluhhhEO/MFp33vGyT+FFI92S0VsA=; b=BA1cLjPR/HE+fLTcDG2rtfcPXXXd/DvtlEwRwl6ZcoNxLKXCg4ZjfN8xmt1qUXZ4cB CPubXEAd+J+sTIWn/TGXU3GlaJICfz8WJkWPjNm9xYIN4Ic6cBZ2CF02DYe5avYVkwuz uyv3JHi0VWd5BTABgaMinktqw35cgR0RbUvObnjG+xDI+kQqgNpBSIqIdV/F1oP8UTX2 ntK7NXWDxJx2TUQB0Unjd+NqN1FBEuM15GJshUiYuho6f3ATcHLeD2Nea32ahzfSK/qf aoyHYhr3iyJ0mnnI5KbP4NgcU3Om+hFKRa0m9vqCSifMd26DXz2nSOYrfPbrAoGLna9J G9Pw== X-Received: by 10.50.57.200 with SMTP id k8mr9143863igq.44.1365479229954; Mon, 08 Apr 2013 20:47:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.135.37 with HTTP; Mon, 8 Apr 2013 20:46:49 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Tue, 9 Apr 2013 09:16:49 +0530 Message-ID: Subject: Re: mr default=local? To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnp7tc1ZYh+Wpzj6pxQJyxRwpgD2E1GVxPwXg4qbu/g7xKUgoCG3brE85FFV9ckbnoW0Crw X-Virus-Checked: Checked by ClamAV on apache.org Hey John, Sorta unclear on what is prompting this question (to answer it more specifically) but my response below: On Tue, Apr 9, 2013 at 9:05 AM, John Meza wrote: > The default mode for hadoop is Standalone, PsuedoDistributed and Fully > Distributed modes. It is configured for Psuedo and Fully Distributed via > configuration file, but defaults to Standalone otherwise (correct?). The mapred-default.xml we ship, has "mapred.job.tracker" (0.20.x/1.x/0.22.x) set to local, or "mapreduce.framework.name" (0.23.x, 2.x, trunk) set to local. This is why, without reconfiguring an installation to point to a proper cluster (JT or YARN), you will get local job runner activated. > Question about the -defaulting- mechanism: > -Does it get the -default- configuration via one of the config files? For any Configuration type of invocation: 1. First level of defaults come from *-default.xml embedded inside the various relevant jar files. 2. Configurations further found in a classpath resource XML (core,mapred,hdfs,yarn, *-site.xmls) are applied on top of the defaults. 3. User applications' code may then override this set, with any settings of their own, if needed. > -Or does it get the -default- configuration via hard-coded values? There may be a few cases of hardcodes, missing documentation and presence in *-default.xml, but they should still be configurable via (2) and (3). > -Or another mechanism? -- Harsh J