Hey Stephen,
Thanks for the reply.
I'm not concerned about the cause at this point as I haven't done
due-diligence yet. I am looking for any tips on how to fix this by hand
(prior to hbck2).
I thought I could trick the master into assigning it by messing with the
row in meta, but I've not been successful yet. I fear that the master
won't do anything unless there's an SCP which I can't easily create.
It sucks because we're sinking all Master operations when it's just NS
operations that are blocked. I thought we had fixed this way back when,
but it seems like we're no better off than we were in early 1.x releases.
On 10/25/18 1:45 PM, Tak-Lon (Stephen) Wu wrote:
Not sure if this is related to
https://issues.apache.org/jira/browse/HBASE-20671
if so, and if you have HBASE-20702 on your branch, when a new cluster that
master starts on the
same root directory (my case is on root directory is on S3),
hbase:namespace table cannot be assigned.
(Sorry that I don't have time to work on the solution, but I locally
removed patch of HBASE-20702)
-Stephen
On Thu, Oct 25, 2018 at 8:12 AM Josh Elser <els...@apache.org> wrote:
I have a cluster on branch-2.0 from a week or two ago where
hbase:namespace is not assigned (haven't figured out why yet), I can't
use any of the normal assign/move shell commands because the Master is
useless as it's not initialized (because hbase:namespace is
unreachable), but I can't figure out how I can get the Master to realize
it needs to assign it.
Do we have this written down somewhere already?
Thanks in advance.
- Josh
