Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 159D7D430 for ; Tue, 18 Dec 2012 20:29:32 +0000 (UTC) Received: (qmail 41274 invoked by uid 500); 18 Dec 2012 20:29:27 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 41076 invoked by uid 500); 18 Dec 2012 20:29:27 -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 41055 invoked by uid 99); 18 Dec 2012 20:29:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 20:29:26 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.223.169] (HELO mail-ie0-f169.google.com) (209.85.223.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 20:29:20 +0000 Received: by mail-ie0-f169.google.com with SMTP id c14so1567670ieb.14 for ; Tue, 18 Dec 2012 12:28:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=uj9rm4W2tmTOk6R9Xcr1tM/mhwy6pNgKsPx7T+lVcbE=; b=eV2IexlZIs1OuilLVF5aOzcafj+Y2PDjyKCc8ox+KG4GNQ3k0JRMk+FAgCkYoY2Nu4 3FdZDceRdRJfbJMYeVcjZ12kwRLXc8zrYb+Gky5WvZOnP8OfmPAgSST41fTI2vghgvdd mBiUQzdeWYD4y+pdDP0NqlC5HlYC0JdHYavDTZ/1GFBFcxJEn7USQDMBYqp9/6etbrfc km6c+UIDzPmoJyrlja127ngJro1o6ENSDM5RBEmF+iluJU+2nvTMQCp8gz8Jt2lAzpJk A0Zq8E0p2VWYcbs11+fumUqIJAQ8BRKK8QVOkFqhdd0kA1ORaNFghSL1IFFQNU0YYb3T SOjg== MIME-Version: 1.0 Received: by 10.50.161.130 with SMTP id xs2mr4402336igb.34.1355862539838; Tue, 18 Dec 2012 12:28:59 -0800 (PST) Received: by 10.64.36.164 with HTTP; Tue, 18 Dec 2012 12:28:59 -0800 (PST) Date: Tue, 18 Dec 2012 15:28:59 -0500 Message-ID: Subject: Misconfiguration of hdfs-site.xml From: Jean-Marc Spaggiari To: user Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlYrKIPNe4TmOyzAfAj+YwaKKmBoZrtGQWD5JSryRjrRgHr187bI7Hv1q7TAVaL0NcRkiv9 X-Virus-Checked: Checked by ClamAV on apache.org Hi, For months now I'm using my hadoop cluster with absolutly nothing related to the drive directory on my hdfs-site.xml file. It seems that it's using the hadoop.tmp.dir directory to store data. My hadoop.tmp.dir is pointing to /home/hadoop/haddop_drive/${user.name} and on my /home/hadoop/haddop_drive directory I can see hadoop and hbase. Now, I want to configure that properly without loosing the data I have. I'm using 1.0.3. Based on the documentation http://hadoop.apache.org/docs/r1.0.3/cluster_setup.html#Site+Configuration it seems I need to setup dfs.data.dir to point to /home/hadoop/haddop_drive. If I add this entry and restart my datanode, will it "simply" continue to point to the same place and find the data he needs? Also, what about dfs.name.dir ? I guess I can simply point it to the same place, right? On /home/hadoop/haddop_drive/hadoop/dfs I have data and name directories. So I'm not sure if I should point the properties above to /home/hadoop/haddop_drive or to /home/hadoop/haddop_drive/dfs. Thanks, JM