Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 2080 invoked from network); 26 Feb 2008 00:09:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2008 00:09:40 -0000 Received: (qmail 10222 invoked by uid 500); 26 Feb 2008 00:09:34 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 10204 invoked by uid 500); 26 Feb 2008 00:09:34 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 10195 invoked by uid 99); 26 Feb 2008 00:09:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2008 16:09:34 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=FS_REPLICA,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.145.54.173] (HELO mrout3.yahoo.com) (216.145.54.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2008 00:08:45 +0000 Received: from SNV-EXPF01.ds.corp.yahoo.com (snv-expf01.ds.corp.yahoo.com [207.126.227.250]) by mrout3.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id m1Q08Hrp041968 for ; Mon, 25 Feb 2008 16:08:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:x-mimeole:content-class:mime-version: content-type:content-transfer-encoding:subject:date:message-id: in-reply-to:x-ms-has-attach:x-ms-tnef-correlator:thread-topic: thread-index:references:from:to:return-path:x-originalarrivaltime; b=wITOR9XrFliWrEIwt+kFmWvkGiDiQt9UM2CSmT7Zfzj7Hgm/7xaYF3fObklKWeyW Received: from SNV-EXVS08.ds.corp.yahoo.com ([207.126.227.8]) by SNV-EXPF01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 25 Feb 2008 16:08:17 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Specifying the positions of replicas Date: Mon, 25 Feb 2008 16:08:16 -0800 Message-ID: <84E52AD05F6F884AAFF3344FE4C95991011E598D@SNV-EXVS08.ds.corp.yahoo.com> In-Reply-To: <256fdd860802251431k3ec970far56f40df654e5e4bb@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Specifying the positions of replicas Thread-Index: Ach3/poNLKSq1PoSSFehr3stMuekMAADPzYw References: <256fdd860802251431k3ec970far56f40df654e5e4bb@mail.gmail.com> From: "dhruba Borthakur" To: X-OriginalArrivalTime: 26 Feb 2008 00:08:17.0789 (UTC) FILETIME=[B04D52D0:01C8780B] X-Virus-Checked: Checked by ClamAV on apache.org Maybe using LOG.warn("function name") will get your stuff into the namenode log file. Thanks, Dhruba -----Original Message----- From: Zhu Huijun [mailto:nautilushj@gmail.com]=20 Sent: Monday, February 25, 2008 2:32 PM To: core-dev@hadoop.apache.org Subject: Specifying the positions of replicas Hi, all, Currently our group want to try some new data layout schemes on Hadoop, but I encounter some problems. In Hadoop, each block has 3 replicas by default. It is said in the documents that two of them are put randomly in the same rack, and the third is put at another rack. This procedure is also clear in the source code of the class org.apache.hadoop.dfs.ReplicationTargetChooser. What I did was adding a simple System.out.println("function name") clause in each function in ReplicationTargetChooser, and intended to check which ones are called to select the target nodes for replicas. However, when I use "./bin/hadoop dfs -copyFromLocal" command to copy some files from the local file system to HDFS, it seems none of the functions in the ReplicationTargetChooser is called, because nothing is printed out on the screen or the log files. I preciate if someone can tell me where I can modify to control the target nodes of replicas. Thank you! Have a nice day! Huijun Zhu