A possible reason could be that the znode associated with this particular
table is not behaving properly. In such case, you can try the following:

Stop Hbase
Stop ZK
Take a backup of ZK data
Restart ZK
Remove the znode
Start Hbase again

After this hopefully your table would be enabled.

Regards,
    Mohammad Tariq



On Thu, Sep 27, 2012 at 2:59 AM, Mohammad Tariq <[email protected]> wrote:

> Yes. Also have a look at the logs of the problematic region if hbck shows
> any inconsistency.
>
> Regards,
>     Mohammad Tariq
>
>
>
> On Thu, Sep 27, 2012 at 2:55 AM, Mohit Anchlia <[email protected]>wrote:
>
>> Which node should I look at for logs? Is this the master node? I'll try
>> hbck.
>>
>> On Wed, Sep 26, 2012 at 2:19 PM, Mohammad Tariq <[email protected]>
>> wrote:
>>
>> > Hello Mohit,
>> >
>> >     Try hbck once and see if it shows any inconsistency. Also, you can
>> try
>> > restarting your cluster and deleting the table again. Having a look at
>> the
>> > logs could also be useful.
>> >
>> > Regards,
>> >     Mohammad Tariq
>> >
>> >
>> >
>> > On Thu, Sep 27, 2012 at 2:24 AM, Mohit Anchlia <[email protected]
>> > >wrote:
>> >
>> > > When I try to disable table I get:
>> > >
>> > >  hbase(main):011:0> disable 'SESSIONID_TIMELINE'
>> > > ERROR: org.apache.hadoop.hbase.TableNotEnabledException:
>> > > org.apache.hadoop.hbase.TableNotEnabledException: SESSIONID_TIMELINE
>> > > Here is some help for this command:
>> > > Start disable of named table: e.g. "hbase> disable 't1'"
>> > >
>> > > But then I try to enable I get:
>> > >
>> > > hbase(main):012:0> enable 'SESSIONID_TIMELINE'
>> > > ERROR: org.apache.hadoop.hbase.TableNotDisabledException:
>> > > org.apache.hadoop.hbase.TableNotDisabledException: SESSIONID_TIMELINE
>> > > Here is some help for this command:
>> > > Start enable of named table: e.g. "hbase> enable 't1'"
>> > >
>> > > I've tried flush, major_compaction also. I tseems it's stuck in
>> > > inconsistent state. Could someone point me to correct direction? I am
>> > using
>> > > 92.1
>> > >
>> >
>>
>
>

Reply via email to