[
https://issues.apache.org/jira/browse/HBASE-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142957#comment-14142957
]
Mikhail Antonov commented on HBASE-12035:
-----------------------------------------
bq. Mark one region only, the first one?
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? From design point of view, first region isn't anything special
and doesn't differ from other regions, so making it carry table-level metadata
looks a bit strange?
Agree that writing status of the table into every region sounds like wasting of
space (or maybe not really..1 million boolean flags - it's 1mb or space, isn't
it?)
> 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)
