[
https://issues.apache.org/jira/browse/HBASE-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945251#comment-16945251
]
Michael Stack commented on HBASE-23103:
---------------------------------------
bq. Master startup needs meta table online as we need to scan meta, and here
want to disable meta.
bq. ...we may still hit problems, for example, the ModifyTableProcedure is only
half done and assume that meta table is disabled, but after restarting, meta
table is enabled, and the procedure can not continue...
So, master comes up, can read hbase:meta (though its state may be in-between)
and we have a stuck procedure. MIght have to do some fixing w/ hbck2 to address
this super-rare scenario (edit of meta is rate * failure of master during meta
edit * fails in middle of cross-family edit).
The alternative of snowflaking hbase:meta in at least three different locations
makes for intrigue and complexity around sequences already hard to decipher.
Any other ideas?
Any ideas around meta state?
Thanks [~zhangduo]
> Survey incidence of table state queries
> ---------------------------------------
>
> Key: HBASE-23103
> URL: https://issues.apache.org/jira/browse/HBASE-23103
> Project: HBase
> Issue Type: Sub-task
> Reporter: Michael Stack
> Priority: Blocker
> Fix For: 3.0.0
>
>
> Task that comes of parent issue. Parent makes it so we go via Master to
> figure state of a table. It is the authority and since the parent issues adds
> being able to enable/disable hbase:meta, table state is now in two places --
> in hbase:meta table... and elsewhere for the hbase:meta's state. Rather than
> have client go to two locations dependent on which table is being asked
> about, parent made it so we went to master. Parent allows that this puts more
> load on the Master. [~zhangduo] brings up the valid concern that it might be
> too much or that dependent on the Master for state puts Master too much
> in-line with read/writes.
> This issue is a survey to figure how much load and how much state-in-master
> could mess up inline read/writes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
