Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 CF192E688 for ; Fri, 11 Jan 2013 17:16:37 +0000 (UTC) Received: (qmail 6825 invoked by uid 500); 11 Jan 2013 17:16:33 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 6703 invoked by uid 500); 11 Jan 2013 17:16:33 -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 6690 invoked by uid 99); 11 Jan 2013 17:16:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 17:16:33 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of prvs=716cbe5f7=afaris@linkedin.com designates 69.28.149.80 as permitted sender) Received: from [69.28.149.80] (HELO esv4-mav04.corp.linkedin.com) (69.28.149.80) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 17:16:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=@linkedin.com; q=dns/txt; s=proddkim1024; t=1357924588; x=1389460588; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=vwb2ZiBFLV60UlI+V06ZBG8hKjnQs4EEYFKWQFrw4Ns=; b=k3d/VgfedNbxUmQpinO5U4wEl+iGmDiiOCUBRb/RAmvJpcYoZ+fO80ZL M7r4xVmFBxEYu0LhKBr2TL5qm7SSkju4715jhL2P4I1OL9XVaUbmR6vN5 9/geJUgmo/XM45AkaedBpmLoq4xrn+OZP5fhH4r24CM/ETGVd1/RmyF+X c=; X-IronPort-AV: E=Sophos;i="4.84,453,1355126400"; d="scan'208";a="34703472" Received: from ESV4-HT02.linkedin.biz (172.18.46.236) by esv4-cas01.linkedin.biz (172.18.46.140) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 11 Jan 2013 09:15:48 -0800 Received: from ESV4-EXC01.linkedin.biz ([fe80::d7c:dc04:aea1:97d7]) by ESV4-HT02.linkedin.biz ([::1]) with mapi id 14.01.0218.012; Fri, 11 Jan 2013 09:15:48 -0800 From: Adam Faris To: "" Subject: Re: services requiring topology conf Thread-Topic: services requiring topology conf Thread-Index: AQHN8B1gMzT86guCCk+TfygIOlwMYJhE5JCA Date: Fri, 11 Jan 2013 17:15:47 +0000 Message-ID: <56D3236F-224C-4933-8CF9-BE8E8DA1C30F@linkedin.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.46.250] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <951E3CA58102474BA3EEB8DD4A38F645@linkedin.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org A patch was submitted for topology documentation, but it doesn't appear to = have made it to any releases. This svn link may help starting at line 1294= . =20 http://svn.apache.org/viewvc?view=3Drevision&revision=3D1411359 =20 Assuming you are using hadoop 1.x and not yarn, the topology script only ne= eds to be on the namenode and jobtracker. As you have noticed it doesn't h= urt anything if you copy the script everywhere as the tasktracker and datan= ode process will ignore it. Try looking at pdsh for controlling compute n= odes and pushing files, but be careful as if you type a bad command it's go= ing to get ran everywhere. http://code.google.com/p/pdsh/ -- Adam On Jan 11, 2013, at 9:01 AM, Bryan Beaudreault w= rote: > The documentation on topology conf (topology.script.file.name) is a littl= e sparse, and while we have it working in our cluster I am trying to make i= t a little easier to configure. >=20 > Currently we upload a python file and conf file to every node in our clus= ter. However I have a feeling that it is only needed on the NameNode(s) an= d perhaps JobTracker. I checked the code for DataNode and see no reference= to this configuration parameter, but I wanted to check with you all before= I stop updating the conf on every one of my nodes. >=20 > Can anyone confirm whether these configuration files only need to be pres= ent on the NameNode/JobTracker, or do they need to be on every node in a cl= uster? >=20 > Thanks