[ https://issues.apache.org/jira/browse/HBASE-21073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657295#comment-16657295 ]
Mike Drob commented on HBASE-21073: ----------------------------------- branch-2 and branch-2.1 are doable, branch-2.0 is proving to be more messy. I'll leave that one until I can iron out the first two though. Might end up creating a separate backport issue for it if we get close to releases on another branch so that the release notes are all accurate. > "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: Mike Drob > Priority: Major > Attachments: HBASE-21073.branch-2.001.patch, > HBASE-21073.branch-2.1.001.patch, HBASE-21073.branch-2.1.002.patch, > HBASE-21073.master.001.patch, HBASE-21073.master.002.patch, > HBASE-21073.master.003.patch, HBASE-21073.master.004.patch, > HBASE-21073.master.005.patch, HBASE-21073.master.006.patch, > HBASE-21073.master.007.patch, HBASE-21073.master.008.patch, > HBASE-21073.master.009.patch, HBASE-21073.master.010.patch, > HBASE-21073.master.011.patch > > > 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)