[ https://issues.apache.org/jira/browse/HBASE-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301625#comment-14301625 ]
stack commented on HBASE-12035: ------------------------------- [~octo47] I went over the patch. It looks good (what about the CellComparator expecting to be able to find ',' delimiters in these new table-specific rows... that works ok?) So, what about migration? Would be sweet to get this into hbase-1.0.1 but that would require it self-migrating. You think that possible? Or we have to wait till hbase-2.0? Thanks. Nice work. > 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-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)