[
https://issues.apache.org/jira/browse/HBASE-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Stepachev updated HBASE-12035:
-------------------------------------
Attachment: HBASE-12035.patch
TableState now only in META
TableState in HTD now deprecated and can be removed from protobuf in future
versions.
Removed HTD from meta
Using RetryCallable
Various tests are fixed
rebuild meta now know about states and rebuild them
MetaTableAccessor renamed to reflect what they actually scan.
migration not yet done.
> 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
> Components: Client, master
> Affects Versions: 2.0.0
> Reporter: Enis Soztutar
> Assignee: Andrey Stepachev
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-12035.patch, HBASE-12035.patch, HBASE-12035.patch,
> HBASE-12035.patch
>
>
> 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)