Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 59BA3E2F2 for ; Fri, 11 Jan 2013 10:24:05 +0000 (UTC) Received: (qmail 74707 invoked by uid 500); 11 Jan 2013 10:24:03 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 74530 invoked by uid 500); 11 Jan 2013 10:24:01 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 74498 invoked by uid 99); 11 Jan 2013 10:24:00 -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 10:24:00 +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 (athena.apache.org: domain of asaf.mesika@gmail.com designates 209.85.214.54 as permitted sender) Received: from [209.85.214.54] (HELO mail-bk0-f54.google.com) (209.85.214.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 10:23:52 +0000 Received: by mail-bk0-f54.google.com with SMTP id je9so828196bkc.13 for ; Fri, 11 Jan 2013 02:23:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=MHHr1foNGVdDWSzePQbY5T76GhQFG1UjDe6fhKb5uL0=; b=00goyvEkB/vvy6jIyh5Ni8xO7T4iXilB08NbaeKhSh9auYGpYv30P0D76iMdiI8co5 XN8xLeIuxdZlHwgDjWGXqztZ6WKsR97iOzhhlCyg7qhms2UnL/SWtPkdXOz9qbbbulxM PZ2JmWp1+YKjKbzP/ISOLbrioM1zZfVx14HqNWhIuj7hauJlf9tH6MOpURAXSYdh1w2M LZmmkIbH0TMG8XzcJRQuHDEsHjw50bIz2VvoP27feszesSmNcjPW8HVyxityqzVjrQ1F niqWDUp9BDzXKmZzLKBTKbxiIAIttxVb+xbNoW+ZIryG/ItOb2nbF9BXzfnMAekdu1Bo yASA== X-Received: by 10.204.153.27 with SMTP id i27mr35428383bkw.116.1357899811547; Fri, 11 Jan 2013 02:23:31 -0800 (PST) Received: from [10.100.101.103] (93-172-21-231.bb.netvision.net.il. [93.172.21.231]) by mx.google.com with ESMTPS id 18sm3640028bkv.0.2013.01.11.02.23.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Jan 2013 02:23:30 -0800 (PST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1283) Subject: Re: HDFS disk space requirements From: "Mesika, Asaf" In-Reply-To: Date: Fri, 11 Jan 2013 12:23:27 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: user@hbase.apache.org X-Mailer: Apple Mail (2.1283) X-Virus-Checked: Checked by ClamAV on apache.org 130 GB raw data will take in HBase since it adds the family name, = qualifier and timestamp to each value, so it can even be 150GB. You can = check it exactly, by loading only one row with one column and see how = much it takes on the HDFS file system (run compaction first). Next, you 5 times that since you have 5 times replication, so = 5x150=3D750GB On Jan 11, 2013, at 5:07 AM, Panshul Whisper wrote: > Hello, >=20 > I have a 5 node hadoop cluster and a fully distributed Hbase setup on = the > cluster with 130 GB of HDFS space avaialble. HDFS replication is set = to 5. >=20 > I have a total of 115 GB of JSON files that need to be loaded into the > Hbase database and then they have to processed. >=20 > So is the available HDFS space sufficient for the operations?? = considering > the replication and all factors? > or should I increase the space and by how much? >=20 > Thanking You, >=20 > --=20 > Regards, > Ouch Whisper > 010101010101