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) Client does an RPC to master everytime a region is relocated
Date Sun, 25 Jan 2015 04:36:35 GMT

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

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

Thank you [~octo47] for having a go at this.  I like what [~enis] says, particularly around
"2. Right after meta onlined master runs sync and updates META with information from hdfs.",
that we should move the schema to meta out of hdfs. Let me give you some feedback over on
rb.

> 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-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