Query on rowkey distribution || Does RS and number of Region related with each other

2018-08-29 Thread Manjeet Singh
Hi All, I have two Question *Question 1 : * I want to understand how rowkey distribution happen if I create my table with out applying any policy but opting prefix salting. Example I have rowkey like SALT_ID_DayStartTimestamp_DayEndTimeStamp_IDTimeStamp So it will look like as below

Re: a table is neither disable or enable

2018-08-29 Thread Antonio Si
Thanks Ted. Antonio. On Wed, Aug 29, 2018 at 4:00 PM Ted Yu wrote: > I doubt the procedure would finish, considering it has run for so long. > > You can check the tail of master log to see if it is stuck. > If it is stuck, see if you can use abort_procedure.rb to stop. > > After the procedure

Re: a table is neither disable or enable

2018-08-29 Thread Ted Yu
I doubt the procedure would finish, considering it has run for so long. You can check the tail of master log to see if it is stuck. If it is stuck, see if you can use abort_procedure.rb to stop. After the procedure is stopped, see if running hbck can fix the issue (I haven't worked with 1.3

Re: a table is neither disable or enable

2018-08-29 Thread Antonio Si
Forgot to mention that all regions of the table is offline now. Wondering if the table will eventually got disable as it has been running for almost 24 hrs now. Thanks. Antonio. On Wed, Aug 29, 2018 at 3:40 PM Antonio Si wrote: > Thanks Ted. > Now that the table is in neither disable or

Re: a table is neither disable or enable

2018-08-29 Thread Antonio Si
Thanks Ted. Now that the table is in neither disable or enable state, will the table eventually got disable completely? >From the "Procedure" tab of the hbase ui, I see the "disable" is still running. Thanks. Antonio. On Wed, Aug 29, 2018 at 3:31 PM Ted Yu wrote: > The 'missing table

Re: a table is neither disable or enable

2018-08-29 Thread Ted Yu
The 'missing table descriptor' error should have been fixed by running hbck (with selected parameters). FYI On Wed, Aug 29, 2018 at 2:46 PM Antonio Si wrote: > Thanks Ted. > > The log says "java.io.IOException: missing table descriptor for > ba912582f295f7ac0b83e7e419351602 > >

Re: a table is neither disable or enable

2018-08-29 Thread Antonio Si
Thanks Ted. The log says "java.io.IOException: missing table descriptor for ba912582f295f7ac0b83e7e419351602 [AM.ZK.Worker-pool2-t6552] master.RegionStates: Failed to open/close ba912582f295f7ac0b83e7e419351602 set to FAILED_OPEN" The version of hbase is 1.3.1 Thanks. Antonio. On Wed,

Re: a table is neither disable or enable

2018-08-29 Thread Ted Yu
Do you have access to master / region logs for when FAILED_OPEN state was noticed ? There should be some hint there as to why some region couldn't open. The length of table DDL is related to number of regions the table has. But the length should be less related to data amount. Which version of

a table is neither disable or enable

2018-08-29 Thread Antonio Si
Hi, We have a table which is stuck in FAILED_OPEN state. So, we planned to drop the table and re-clone the table from an old snapshot. We disabled the table, but the disable procedure has been running for more than 20 hrs. I went to hbase shell and found out "is_disabled" and "is_enabled" both