Re: Disable table command hangs in hbase shell in HBase 1.1.2

On Tue, Feb 16, 2016 at 8:30 AM, Anthony Nguyen wrote: > Hi all, > > I'm running into an issue in HBase 1.1.2 where after a cluster is running > for some time, disabling a table in the shell has no effect, hanging until > the timeout limit is reached. Looking at the

Disable table command hangs in hbase shell in HBase 1.1.2

Hi all, I'm running into an issue in HBase 1.1.2 where after a cluster is running for some time, disabling a table in the shell has no effect, hanging until the timeout limit is reached. Looking at the master logs there is only one message that has anything to do with it: 2016-02-12 13:16:23,237

Re: enable/disable table permission

, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise

Re: enable/disable table permission

was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems

Re: enable/disable table permission

and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise on attempting to maintain some of the previous semantics. Andrew Purtell commented to this in HBASE-6188: quote CREATE -(DDL) CreateTable

Re: enable/disable table permission

or * the user is the table owner AND has the CREATE permission I believe the original intent here was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems

Re: enable/disable table permission

it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise on attempting to maintain some of the previous semantics. Andrew Purtell commented to this in HBASE-6188: quote CREATE -(DDL

Re: enable/disable table permission

: * ADMIN permission or * the user is the table owner AND has the CREATE permission I believe the original intent here was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply

Re: enable/disable table permission

AND has the CREATE permission I believe the original intent here was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems

Re: enable/disable table permission

or * the user is the table owner AND has the CREATE permission I believe the original intent here was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either

Re: enable/disable table permission

I believe the original intent here was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise

Re: enable/disable table permission

here was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise on attempting

Re: enable/disable table permission

a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise on attempting to maintain some

Re: enable/disable table permission

a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise on attempting

Re: enable/disable table permission

to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise on attempting to maintain some of the previous semantics

Re: enable/disable table permission

I believe the original intent here was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE

enable/disable table permission

According to http://hbase.apache.org/book/hbase.accesscontrol.configuration.html#d2566e5780, the Enable/Disable operation is controlled by the Admin permission. However, it seems to be controlled instead by the Create permission. Is this a bug or a typo in the documentation? hbase(main):002:0

Re: enable/disable table permission

Here is related code from AccessController: {code} public void preDisableTable(ObserverContextMasterCoprocessorEnvironment c, byte[] tableName) ... requirePermission(disableTable, tableName, null, null, Action.ADMIN, Action.CREATE); {code} requirePermission() iterates through the above

Re: enable/disable table permission

Sounds like either permission is sufficient. Either way, the documentation could be improved. Thanks. On Tue, Feb 25, 2014 at 3:22 PM, Ted Yu yuzhih...@gmail.com wrote: Here is related code from AccessController: {code} public void

Re: enable/disable table permission

I don't really understand how HBase permission is expected to work then. A user needs the Create permission in order to be able to create their own tables. But that permission also allows them to drop and alter the tables created by others. Even if those operations are set up to only work when a

Re: enable/disable table permission

the original intent here was that if you created a table, you should be able to disable and modify it. After HBASE-6188, the check in enable/disable table is simply for either ADMIN or CREATE permission. This seems to be the best compromise on attempting to maintain some of the previous semantics

Re: disable table

that the master is responsible for the overall maintenance of the no of tables and their respective states, it seeks the help of ZK to do it and that is where the states are persisted. Also there are few cases where the enable and disable table are having some issues due to some race conditions

Re: disable table

master. As you understand correctly that the master is responsible for the overall maintenance of the no of tables and their respective states, it seeks the help of ZK to do it and that is where the states are persisted. Also there are few cases where the enable and disable table

Re: disable table

and disable table are having some issues due to some race conditions in the 0.92 versions, In the latest version we are trying to resolve them. You can attach the master and RS logs to identify exactly what caused this problem in your case which will be really help ful so that I can

Re: disable table

be fixed in the kernel. Regards Ram -Original Message- From: Mohit Anchlia [mailto:mohitanch...@gmail.com] Sent: Thursday, September 27, 2012 5:09 AM To: user@hbase.apache.org Subject: Re: disable table I did /hbase/table

RE: disable table

the problem is because of compression. Regards Ram -Original Message- From: Mohit Anchlia [mailto:mohitanch...@gmail.com] Sent: Thursday, September 27, 2012 9:55 PM To: user@hbase.apache.org Subject: Re: disable table I did restart entire cluster and still that didn't help. Looks like

Re: disable table

: 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

Re: disable table

. Having a look at the logs could also be useful. Regards, Mohammad Tariq On Thu, Sep 27, 2012 at 2:24 AM, Mohit Anchlia mohitanch...@gmail.com wrote: When I try to disable table I get: hbase(main):011:0 disable 'SESSIONID_TIMELINE' ERROR

Re: disable table

: Mohit Anchlia mohitanch...@gmail.com To: user@hbase.apache.org Sent: Wednesday, 26 September 2012 4:54 PM Subject: disable table When I try to disable table I get: hbase(main):011:0 disable 'SESSIONID_TIMELINE' ERROR: org.apache.hadoop.hbase.TableNotEnabledException

Re: disable table

On Thu, Sep 27, 2012 at 2:24 AM, Mohit Anchlia mohitanch...@gmail.com 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

Re: disable table

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 mohitanch...@gmail.com wrote: When I try to disable table I get: hbase(main):011:0 disable 'SESSIONID_TIMELINE' ERROR

Re: disable table

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 mohitanch...@gmail.com wrote: When I try to disable table I

Re: disable table

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 mohitanch...@gmail.com wrote: When I try to disable table I get

Re: disable table

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 mohitanch...@gmail.com wrote: When I try to disable table I get

Re: disable table

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

RE: disable table

. Also there are few cases where the enable and disable table are having some issues due to some race conditions in the 0.92 versions, In the latest version we are trying to resolve them. You can attach the master and RS logs to identify exactly what caused this problem in your case which

Disable table works, but truncate says table does not exists

Hi there, I have a strange situation on one of my tables in HBase: * disable/describe 'my_table' works (using HBase shell) * truncate/drop doesn't - yells table does not exists. How do I fix it? HBase Shell quote: hbase(main):003:0 disable 'my_table' 0 row(s) in 0.0480 seconds

Re: Disable table works, but truncate says table does not exists

I had the same problem a while ago. I fixed this way: Stopped hbase, connect to Zookepper (hbase zkcli), My table was in /hbase/tables. Deleted this entry. What was happening in my case was that zookepper locked the table in a strange way. I'm using cloudera distribution. Miguel Costa

Re: Not able to Disable table : ERROR: org.apache.hadoop.hbase.RegionException: Retries exhausted, it took too long to wait for the table testtable2 to be disabled.

See this: http://comments.gmane.org/gmane.comp.java.hadoop.hbase.user/13441 --Suraj On Mon, Apr 16, 2012 at 9:20 PM, Narayanan K knarayana...@gmail.com wrote: Hi all, Any advise on this? Thanks, Narayanan On Mon, Apr 16, 2012 at 3:27 PM, Narayanan K knarayana...@gmail.com wrote: Hi,

Not able to Disable table : ERROR: org.apache.hadoop.hbase.RegionException: Retries exhausted, it took too long to wait for the table testtable2 to be disabled.

Hi, I am not able to disable an HBase table. Checked out the link: https://issues.apache.org/jira/browse/HBASE-2812 But is this resolved in 0.90.3.? If so, why is the error occurring after repeated trials. The details of our Hbase installations are as follows: $ hbase HBase Shell; enter

Re: disable table, alter table, and merge regions

) reseted all other table properties to default values. For example version was reset to 3, compression was reset to NONE etc. [I think this is known issue with open Jira] (B) We wanted to go back to previous table properties. Now after multiple retires we were not able to disable table

disable table, alter table, and merge regions

we were not able to disable table (even restarting cluster didn't helped). Most likely if clients are hitting hard (in this case ~10k qps) on HBase table, it takes forever to disable a table. So we stopped all clients and then were able to disable table and altered table properties to desired

Re: Unable to disable table, DroppedSnapshotException, .META. inconsistency

Something else I'm seeing in the web interface: Master has: surveySession,,1289578320747.edb037e879e0df212556205751f60a39. ds4.internal:60030 But ds4 has: surveySession,,1289521116693.92f678a946ea7dfc999564c202132ecf. stores=2, storefiles=0, storefileSizeMB=0,

Re: Unable to disable table, DroppedSnapshotException, .META. inconsistency

Doesn't the DroppedSnapshotException also include a stack trace? Else it's going to be very hard to guess why it's failing (maybe lzo isn't properly configured, I see you're using it). It seems the first region in your table split once, but the parent somehow revived. At least that's one way it

Unable to disable table, DroppedSnapshotException, .META. inconsistency

I'm unit testing some of our internal framework that interacts with hbase (version cdh3b3 = 0.89.20100924+28). The unit test is small inserting and updating ~100 rows. My unit test expects the hbase table to be empty when starting. So I go into hbase shell table disable the table, drop it,