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 559F211499 for ; Tue, 16 Sep 2014 22:12:42 +0000 (UTC) Received: (qmail 82350 invoked by uid 500); 16 Sep 2014 22:12:36 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 82234 invoked by uid 500); 16 Sep 2014 22:12:36 -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 82222 invoked by uid 99); 16 Sep 2014 22:12:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 22:12:35 +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 (nike.apache.org: domain of yusaku@hortonworks.com designates 209.85.217.178 as permitted sender) Received: from [209.85.217.178] (HELO mail-lb0-f178.google.com) (209.85.217.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 22:12:09 +0000 Received: by mail-lb0-f178.google.com with SMTP id c11so708430lbj.9 for ; Tue, 16 Sep 2014 15:12:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=gk0+rVU1NcST94ZoAgZX7XRGLnYYyDWe2VuKnoieTxw=; b=c/5jKJbOiPigrxhjVSfMyiIw1Z9MAxWovr9WVFCED9tOlVUPLfFqw1QTzdBSFySGsy QmQwyqKQ/pGSFZGjH7vt5POYp1oTTrTk+CJ7zf1apKq5xw9gHR/W7oSgUX7qt1/0cgks 7+WCCxLdU/zVCW60Q5HkjV0bPrc2RLI5MZsC1JdCpfx5gsIBdsNA8weiPvMuPh0w/WLt 2OtILP+OBBBmd6o6NSC0hrf+8gKWAd924fgCHhYGm7ztG8kJkXVjq9bBJsyqjmi75v6o jO0LxjMYOBkrsgUg8p0bJDQggteudmpluv3Luqd9h0vSTL36iRz6t32vJHX/lz9FeZXr gT6w== X-Gm-Message-State: ALoCoQldPHtVgwGWjKK5cnZzzDczYNcKluayG0EK1lMLSDSph/6IY5pqkY6RJTLWwwa5Vl7zEGw6P+Pd0W6u3+vyBHWKQwo95WWM9qPiAXUvVWuw5bRMbro= MIME-Version: 1.0 X-Received: by 10.152.243.34 with SMTP id wv2mr39649422lac.45.1410905528399; Tue, 16 Sep 2014 15:12:08 -0700 (PDT) Received: by 10.112.166.10 with HTTP; Tue, 16 Sep 2014 15:12:08 -0700 (PDT) In-Reply-To: References: Date: Tue, 16 Sep 2014 15:12:08 -0700 Message-ID: Subject: Re: DataNode not recognising available disk space From: Yusaku Sako To: "user@hadoop.apache.org" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Charles, If the newly added slave node has an extra disk that the other nodes don't have, then you will have to do the following on the Ambari Web UI so that "dfs.data.dir" is reflected to include this extra drive for that node: * Go to Services > HDFS > Configs * Click on "Manage Config Groups" link * Create a new HDFS Configuration Group (name it appropriately), add the slave host in question to that group, and Save. * In the list of configs for HDFS, you will see "DataNode directories" with the current directories set up for DataNodes for all other hosts. * Click on the "+" next to "DataNode directories" and list out all the drives for this new DataNode. * Save the configuration changes. * Restart the DataNode. * Ambari (and HDFS) should start reflecting the added disk space. I hope this solves your problem. FYI, there's an Ambari-specific mailing list at user@ambari.apache.org that you can subscribe by sending an email to user-subscribe@ambari.apache.org. Thanks, Yusaku On Tue, Sep 16, 2014 at 5:28 AM, Charles Robertson wrote: > Hi all, > > I've added a new slave node to my cluster with a (single) larger disk size > (100Gb) than on the other nodes. However, Amabri is reporting a total of 8.6 > Gb disk space. lsblk correctly reports the disk size. > > Does anyone why this might be? As I understand things you need to tell HDFS > how much space *not* to use, and it will use what it needs from the rest. > > (BTW this is not the same data node in my other question on this list, > "Cannot start DataNode after adding new volume.") > > Thanks, > Charles -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.