[jira] [Commented] (HBASE-12035) Client does an RPC to master everytime a region is relocated

["stack (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-12035:
-------------------------------

Good one.

It was wrong when it was a zk client call figuring if table enabled/disabled.  It is also wrong having client going to master to figure is 'table is enabled/disabled'.

Could we mark meta table when region is offline in a way that stops the client in its tracks?  Client can infer table disabled if it has too from meta state.

> Client does an RPC to master everytime a region is relocated
> ------------------------------------------------------------
>
>                 Key: HBASE-12035
>                 URL: https://issues.apache.org/jira/browse/HBASE-12035
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Enis Soztutar
>             Fix For: 2.0.0
>
>
> HBASE-7767 moved table enabled|disabled state to be kept in hdfs instead of zookeeper. isTableDisabled() which is used in HConnectionImplementation.relocateRegion() now became a master RPC call rather than a zookeeper client call. Since we do relocateRegion() calls everytime we want to relocate a region (region moved, RS down, etc) this implies that when the master is down, the some of the clients for uncached regions will be affected. 
> See HBASE-7767 and HBASE-11974 for some more background. 



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