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 15F3CC2B6 for ; Tue, 7 Aug 2012 16:58:17 +0000 (UTC) Received: (qmail 48918 invoked by uid 500); 7 Aug 2012 16:58:15 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 48852 invoked by uid 500); 7 Aug 2012 16:58:15 -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 48843 invoked by uid 99); 7 Aug 2012 16:58:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2012 16:58:15 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com designates 74.125.82.169 as permitted sender) Received: from [74.125.82.169] (HELO mail-we0-f169.google.com) (74.125.82.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2012 16:58:09 +0000 Received: by weys10 with SMTP id s10so3726234wey.14 for ; Tue, 07 Aug 2012 09:57:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=EKOdcuV6YQPtp99Z4kD7OfRWAfbNMtmXcmhztnGn7gc=; b=zHo2CLLCNnhIdEGq3/K0gNuayT6BSpA5ID9M9OR5IKuo0phlgDU/iqNwr0JWuaRW30 Bu+Ebv2S95JutYwupNYUg4ty6BVEuTAyWw/hhvv/cinbW3XxTFgIxjpsuzEK4+Jtczj/ qXvlrVuxdp+tguKHfVvIaYiE34AtCCK3INdPa231VvIzAxOhnC4zl/oWf5uD0IvCb3La 13izYkOYz4YZ/rdX/QfmO39grNtQJIlAOWZZtHJ03qrbLXStJDHAHWvhNMaHDytGkKvH aHvf0A1YuvbcjdyUzPl7hk4J+LOhwrVmopY0EjcKz8VL0/xCAHXjAX3llnjZYvdHNiS8 UIfA== MIME-Version: 1.0 Received: by 10.216.238.27 with SMTP id z27mr7582570weq.81.1344358668454; Tue, 07 Aug 2012 09:57:48 -0700 (PDT) Received: by 10.216.148.194 with HTTP; Tue, 7 Aug 2012 09:57:48 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Aug 2012 09:57:48 -0700 Message-ID: Subject: Re: Hbase- Hadoop DFS size not decreased even after deleting a column family From: Ted Yu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=0015173ffa26e24ad104c6afe4cf X-Virus-Checked: Checked by ClamAV on apache.org --0015173ffa26e24ad104c6afe4cf Content-Type: text/plain; charset=ISO-8859-1 Looking at TableDeleteFamilyHandler, I see: protected void handleTableOperation(List hris) throws IOException { // Update table descriptor in HDFS HTableDescriptor htd = this.masterServices.getMasterFileSystem().deleteColumn(tableName, familyName); // Update in-memory descriptor cache this.masterServices.getTableDescriptors().add(htd); MasterFileSystem.deleteColumn() calls: HTableDescriptor htd = this.services.getTableDescriptors().get(tableName); htd.removeFamily(familyName); I will dig some more. But looks like there is a bug. On Tue, Aug 7, 2012 at 9:21 AM, Stack wrote: > On Tue, Aug 7, 2012 at 9:59 AM, prem yadav wrote: > > Hi Stack, > > yes . I can still see the column family. > > > > we ran the following command too: > > > > fs -dus /hbase/// and it > > returned a large value which means that the space has not been reclaimed. > > The hbase version we are running is 0.94.1. > > > > is there a manual way to force reclaim the space? > > > > You could delete the column family from hdfs under each region. > Anything in the logs around the remove of the column family? Maybe we > just don't do the delete cleanup in hdfs when we drop a cf (I've not > checked)? > > St.Ack > --0015173ffa26e24ad104c6afe4cf--