[
https://issues.apache.org/jira/browse/HBASE-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944003#comment-16944003
]
Michael Stack commented on HBASE-23103:
---------------------------------------
Did a rough survey. Incidence is close to zero where we go to ask table state;
just when we are doing admin on table... which requires the Master. Will do
some more...
What about case where an errant user tool that keeps asking for table state.
This would be user putting load on Master. Could warn against it?
Otherwise, I suppose could update the hbase:meta zk to handle table state but
then the client has to look in two places....
> 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)
