[
https://issues.apache.org/jira/browse/HBASE-21073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646955#comment-16646955
]
Mike Drob commented on HBASE-21073:
-----------------------------------
bq. I have no idea what happens if we try to scan one of the user space tables.
We read the table region locations out of meta, try to connect to the
previously hosting region server, and then fail with connection refused. The
ergonomics of this are not great, but I think maybe we can leave it for follow
on work.
bq. RSRpcServices can try to reject requests from non-replication peers...
bq. I have no idea what happens if we try to come up in a repair mode when
replication is enabled.
Replication doesn't apply to system tables, so that's why this never gets set
up, I think. It's ok to ignore that I think.
Another open question though - should we try to fold this in to the maintenance
mode features of HBASE-16008, where it is tracked via ZK?
> "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.master.001.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)
