[
https://issues.apache.org/jira/browse/HBASE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-12203.
---------------------------
Resolution: Invalid
Resolving as invalid. Context has changed. Some of what Andrey describes in
here is being done (i.e. mirroring of state to zk and state being in a table in
hbase, hbase:meta). Resolving.
> 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: 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
> Alternative way2:
> 1. Extend RS api with getTableState() call
> 2. Each RS will be able to cache table states
> 3. Clients will call RS instead of master or zk
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
