hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12035) Keep table state in META
Date Tue, 10 Feb 2015 22:29:12 GMT

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

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

Since've not published a release where we go via master for state, hopefully we'll never have
to do one of the migration steps.  We can file issue if an issue migrating.  I applied to
master branch but there are a lot of conflicts getting this into branch-1.  If you have a
chance [~octo47], take a look since you are more familiar w/ the patch.  FYI, going forward,
add a version as suffix to your patch name and increment it as you add a new one; it makes
life easier on the committer.  Thanks for the great work [~octo47]

> Keep table state in META
> ------------------------
>
>                 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: 12035v2.txt, HBASE-12035 (1) (1).patch, HBASE-12035 (1) (1).patch,
HBASE-12035 (1).patch, HBASE-12035 (2).patch, HBASE-12035 (2).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-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)

Mime
View raw message