Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1041610717.1233160439984.JavaMail.jira@brutus>
Date: Wed, 28 Jan 2009 08:33:59 -0800 (PST)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-845) disable then drop table is messy when
 table is > 4 or 5 M rows
In-Reply-To: <915877638.1219725584263.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated HBASE-845:
-------------------------------------

    Attachment: hbase-845.patch

Patch that modifies HCM.isTableEnabled so that it returns the true state of the the table.

> disable then drop table is messy when table is > 4 or 5 M rows
> --------------------------------------------------------------
>
>                 Key: HBASE-845
>                 URL: https://issues.apache.org/jira/browse/HBASE-845
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>         Attachments: hbase-845.patch
>
>
> In current trunk, if i load a table of 8M rows and then try and delete it, the disable returns saying the table was successfully deleted but when I then try to drop the table, it says table not disabled.  I run the disable/drop cycle a few more times and still fails.  Eventually, if I wait long enough, it succeeds.   Maybe the table drop should just block if table is seen to have disabled regions in it.  As is, its a little disorientating the way it works.  Could lead admins to distrust status messages emitted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.