Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <459481511.1247173094961.JavaMail.jira@brutus>
Date: Thu, 9 Jul 2009 13:58:14 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Created: (HBASE-1636) disable and drop of table is flakey
 still
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

disable and drop of table is flakey still
-----------------------------------------

                 Key: HBASE-1636
                 URL: https://issues.apache.org/jira/browse/HBASE-1636
             Project: Hadoop HBase
          Issue Type: Bug
            Reporter: stack


Just now, cheddar up on IRC had table of 2k regions.  A disable and drop gave him 2k rows in meta of historian info.  He couldn't progress.  Had to make below script for him:

{code}
meta = HTable.new(".META.")
historian = "historian:"
scanner = meta.getScanner([historian].to_java(java.lang.String))
while (result = scanner.next())
      meta.deleteAll(result.getRow())
end
exit 0
{code}

This flakey disable/enable/drop is frustrating users.  Need to fix.

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