[
https://issues.apache.org/jira/browse/HBASE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163622#comment-14163622
]
Andrey Stepachev commented on HBASE-12203:
------------------------------------------
[~stack] I agree, that zk is not a good solution here, updated jira description
with alternative path.
before starting HBASE-7767 I tried to do that as table, but found myself adding
checks similar to if (table is meta) in most all places, where meta is checked.
for me that looks like a hack.
may be we should reconsider table state caches in each region server once more?
> Remove Master from table status query path.
> -------------------------------------------
>
> Key: HBASE-12203
> URL: https://issues.apache.org/jira/browse/HBASE-12203
> Project: HBase
> Issue Type: Improvement
> Components: Client, master
> Affects Versions: 2.0.0
> Reporter: Andrey Stepachev
> Priority: Minor
> Fix For: 1.0.0, 2.0.0
>
>
> With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a
> good cleanup, but we put additional (substantial) load on master. Some client
> requests use checks for table state (for example HBASE-12035).
> Thats is why patch was not back ported to branch1 (HBASE-11978)
> Lets replicate state back to zk, but as a mirror of table states.
> What can be done:
> 1. TableStateManager would push table state changes to zk
> 2. Return back ZKTableStateClientSideReader.
> Alternative way:
> 1. Move table statuses to separate table like namespaces
> 2. Issue statuses requests against this table
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
