[
https://issues.apache.org/jira/browse/HBASE-25290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235975#comment-17235975
]
Duo Zhang commented on HBASE-25290:
-----------------------------------
{quote}
but what if it is a procedure that needs fixing or an alignment of meta and
procedure state that needs reconciliation? These would require the Master be
involved?
{quote}
I think this implies that, we should have different levels for the maintennance
mode. IIRC I've brought this up before when reviewing the HBCKSCP, where we
want to force assign a region. In HBCKSCP we will scan meta to find 'Unknown
Region Server', and I asked that what if we want to fix meta assignment? Since
meta is not online we can not scan meta. I can not recall your answer but
anyway, since we meet the same problem again, I think it is a common case when
fixing a broken cluster. Let's find out a solution then.
{quote}
Minicluster starts a Master and a RegionServer in same process. Could we base
master maintenance mode ('single-user') on a version of minicluster? Then you
could proceed with your disentangling Master and RS project?
{quote}
Oh, this is an interesting proposal. I think technically it could work but I'm
not sure if it is easy to be used by operators. Do you think I should implement
a prototye first or let's see if starting a mini cluster based on a HDFS in
production is a good choice? Maybe we will be in trouble when kerberos is
enabled? Not sure.
Thanks.
> Remove table on master related code
> -----------------------------------
>
> Key: HBASE-25290
> URL: https://issues.apache.org/jira/browse/HBASE-25290
> Project: HBase
> Issue Type: Sub-task
> Components: Balancer, master
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> This could be a start of the HBASE-15549 feature branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
