User tables being in transition shouldn't impact the master's ability to
finish initializing.
You need to look through the master logs for a message about what
initialization is in a holding pattern about. The most common things are
waiting for the meta region to be online or the namespace table
There's a quick work-around.
All regions get stuck when trying assigning themselves to host 'dtla1apps21'
(from log message). It indicates the RS on that host how some becomes
problematic.
In this case, you can stop the RS on that host which will trigger all STUCK
regions to assign themselves
hi Sean??
My hbase version is hbase2.1.0+cdh6.1.0 , And I've seen the logs of HBase
master, but there are only some RIT status logs , which are as follows
?? 2019-10-11 15:12:00,696 WARN org.apache.hadoop.hbase.master.CatalogJanitor:
CatalogJanitor is disabled! Enabled=true,
what version of hbase are you using?
If master is still initializing, then probably one of the regions in
transition is the region for meta, or a region for a system table (e.g.
hbase:namespace). You should check the master logs to figure out which one
and what their state is.
On Fri, Oct 11,
hi ,guys:
My HBase made the following mistakes when creating a build table or disable
table
" ERROR: org.apache.hadoop.hbase.PleaseHoldException: Master is initializing
at
org.apache.hadoop.hbase.master.HMaster.checkInitialized(HMaster.java:2998)
at
