[
https://issues.apache.org/jira/browse/HBASE-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143369#comment-14143369
]
stack commented on HBASE-12035:
-------------------------------
bq. .... so making it carry table-level metadata looks a bit strange?
Its odd, yeah. Any other ideas?
Trying to get master out of the read/write path and NOT have us introduce new
tables just to hold a state that will rarely be other than the default of 'on'.
bq, ...When HRS hosting first region of the table failed, or first region is
being split or moved - during that time nobody would be able to find out the
status of the table?
Thats right. Table is 'unavailable' sort-of anyways.
> 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
> Priority: Critical
> 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)
