hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12203) Remove Master from table status query path.
Date Wed, 08 Oct 2014 15:23:35 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163611#comment-14163611
] 

stack commented on HBASE-12203:
-------------------------------

What did you think of the discussion over on HBASE-12035 [~octo47]?  Would be cool if we didn't
have to add new functionality to zk -- even as a cache-only. [~enis] mentions the namespace
table over on HBASE-12035... could this keep table state too?

> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message