[
https://issues.apache.org/jira/browse/HBASE-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302607#comment-14302607
]
stack commented on HBASE-12035:
-------------------------------
bq. Migration can be made in TableStateManager, it can read states from zk and
update meta accordingly.
This sounds great.
bq. If we don't want to support states in zk (that could break some apps, that
are rely state in zk instead), we can make migration.
I would say that is you were reading from zk directly, its ok that you are
broken when you go to branch-1. We can write up a release note when it goes in
and call it out loudly.
> 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-12035.patch, HBASE-12035.patch, 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)
