Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <9940EDF3-192D-4D99-9FD1-D509CC341D7E@gmail.com>
References: <9940EDF3-192D-4D99-9FD1-D509CC341D7E@gmail.com>
Date: Thu, 9 Aug 2012 08:00:14 -0400
Message-ID: 
 <CAPQV63Vd=ZUzT=QCchKkWgC=rt9-t_3BmUF6UHS5ygFSAqXF0w@mail.gmail.com>
Subject: Re: how to delete a zombie table permanently?
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
To: user@hbase.apache.org
Content-Type: text/plain; charset=UTF-8

Hi Henry,

I faced the same issue not so long time ago...

Can you take a look at what you have in zookeeper under /hbase/table ?

If you table is there, that's why you see it on the list. Simply
remove it from zookeeper.

You can also take a look there: https://issues.apache.org/jira/browse/HBASE-6294

JM

2012/8/9, henry.kim <henry.jykim@gmail.com>:
> hi, hbase users.
>
> I got a problem when I am testing coprocessors which is released at base
> 0.92.1.
>
> here is the hbase shell outputs
>
> ----------------
> hbase(main):001:0> truncate 'blog'
> Truncating 'blog' table (it may take a while):
>
> ERROR: Unknown table blog!
>
> Here is some help for this command:
>   Disables, drops and recreates the specified table.
>
>
> hbase(main):002:0> list
> TABLE
>
>
> blog
>
>
> counter
>
>
> sidx
>
>
> 3 row(s) in 15.3610 seconds
> ----------------
>
> yes, table 'blog' is a zombie I think.
>
> there was some big stress from coprocessors which is using
> RegionServerObserver interfaces.
>
> how could I fix this situation?