[
https://issues.apache.org/jira/browse/HBASE-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-23103.
-----------------------------------
Assignee: Michael Stack
Resolution: Information Provided
Ok. The discussion here has good info but is moot in light of the form the
parent issue took on commit. The parent no longer goes via master to find table
state. That decision/development has been put off for now. Instead master issue
adds meta table state as a method in Registry and adds an implementation to
ZKAsyncRegistry that does lookup into zk, bypassing Master. For now resolving
as 'Information Provided'. We'll be back to this topic after Master-based
Registry lands. This latter project looks to change nature of Master from
background janitorial player to active participant in data
> 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
> Assignee: 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)
