[
https://issues.apache.org/jira/browse/HBASE-21073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642023#comment-16642023
]
stack commented on HBASE-21073:
-------------------------------
bq. stack - is this the same thing as HBASE-21191?
No. HBASE-21191 is about our taking a holding pattern when no procedure for
hbase:meta assign and then ditto, later, if none for hbase:namespace.
This issue is about a more comprehensive state where the master come up in a
general "single-user" type mode with aspects such as UI and other facility are
available, all procedures WALs have been loaded, and hbase:meta has been 'read'
w/o the need of a separate regionserver to host hbase:meta region. You'd then
be able to poke at the Master and effect various repairs.
> "Maintenance mode" master
> -------------------------
>
> Key: HBASE-21073
> URL: https://issues.apache.org/jira/browse/HBASE-21073
> Project: HBase
> Issue Type: Sub-task
> Components: amv2, hbck2, master
> Reporter: stack
> Assignee: stack
> Priority: Major
>
> Make it so we can bring up a Master in "maintenance mode". This is parse of
> master wal procs but not taking on regionservers. It would be in a state
> where "repair" Procedures could run; e.g. a Procedure that could recover meta
> by looking for meta WALs, splitting them, dropping recovered.edits, and even
> making it so meta is readable. See parent issue for why needed (disaster
> recovery).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
