Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 76006 invoked from network); 2 Jul 2010 02:51:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Jul 2010 02:51:58 -0000 Received: (qmail 3524 invoked by uid 500); 2 Jul 2010 02:51:56 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 3192 invoked by uid 500); 2 Jul 2010 02:51:54 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 3184 invoked by uid 99); 2 Jul 2010 02:51:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jul 2010 02:51:54 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eltonsky9404@gmail.com designates 209.85.216.169 as permitted sender) Received: from [209.85.216.169] (HELO mail-qy0-f169.google.com) (209.85.216.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jul 2010 02:51:47 +0000 Received: by qyk32 with SMTP id 32so216486qyk.14 for ; Thu, 01 Jul 2010 19:50:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=7HJPW99N3q4Jr4Qgv1xJ+COs0qj+STo9YhdPMxRUNag=; b=Si3e57718qy9+SzXPF2Q6eUkPguankoht96QgJGD9B7pOVoqC+0ms1KS4Q+NfAf0XH qWNs6MT/LfzbocmducCj6KleD1C8OwVH8Y+sCPwTIaYEqpTPGsrgSpOm1WEQ5+8QVfmn pXpbBZzBVfYDa6b+pO/L6an586QHdN3kwlKvE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=s1rP3JnMG3IWVeL1qpVCiwuuYFyTwZg18iLUb5pRqHfYPItf/NkHp9+fVvapqu1bxV ZQMDVbQ8XXRGyb7MM2VBwLMYnWm7fyWzlwVYFDEibeSYkfz8LY4z9D6CZuiWZEdx7BbO lXOWT2Cjr6MWyDqYVSs5sD/Nblwh0LHa95AxQ= MIME-Version: 1.0 Received: by 10.224.6.77 with SMTP id 13mr13328qay.19.1278039026383; Thu, 01 Jul 2010 19:50:26 -0700 (PDT) Received: by 10.224.89.18 with HTTP; Thu, 1 Jul 2010 19:50:26 -0700 (PDT) Date: Fri, 2 Jul 2010 12:50:26 +1000 Message-ID: Subject: problem with rack-awareness From: elton sky To: common-user Content-Type: multipart/alternative; boundary=0015175cd59a2d3b7f048a5ea6cc X-Virus-Checked: Checked by ClamAV on apache.org --0015175cd59a2d3b7f048a5ea6cc Content-Type: text/plain; charset=ISO-8859-1 hello, I am trying to separate my 6 nodes onto 2 different racks. For test purpose, I wrote a bash file which smply returns "rack0" all the time. And I add property "topology.script.file.name" in core-site.xml. When I restart by start-dfs.sh, the namenode could not find any datanode at all. All datanodes are lost somehow. If I remove "topology.script.file.name" from conf, things back to normal, i.e. all datanodes are under "default-rack". I don't why datanode couldn't register to namenode when using rack. Any ideas? --0015175cd59a2d3b7f048a5ea6cc--