[ https://issues.apache.org/jira/browse/HBASE-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594229#comment-13594229
]
Hadoop QA commented on HBASE-3171:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12572207/HBASE-3171-v5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 63 new or modified
tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the total number of
javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version
1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number
of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
org.apache.hadoop.hbase.replication.TestReplicationQueueFailover
org.apache.hadoop.hbase.master.TestMasterFailover
{color:red}-1 core zombie tests{color}. There are 2 zombie test(s): at org.apache.hadoop.hbase.master.TestMasterNoCluster.testCatalogDeploys(TestMasterNoCluster.java:329)
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/4683//console
This message is automatically generated.
> Drop ROOT and instead store META location(s) directly in ZooKeeper
> ------------------------------------------------------------------
>
> Key: HBASE-3171
> URL: https://issues.apache.org/jira/browse/HBASE-3171
> Project: HBase
> Issue Type: Improvement
> Components: Client, master, regionserver, Zookeeper
> Reporter: Jonathan Gray
> Attachments: HBASE-3171.patch, HBASE-3171-v2.patch, HBASE-3171-v3.patch, HBASE-3171-v4.patch,
HBASE-3171-v5.patch
>
>
> Rather than storing the ROOT region location in ZooKeeper, going to ROOT, and reading
the META location, we should just store the META location directly in ZooKeeper.
> The purpose of the root region from the bigtable paper was to support multiple meta regions.
Currently, we explicitly only support a single meta region, so the translation from our current
code of a single root location to a single meta location will be very simple. Long-term,
it seems reasonable that we could store several meta region locations in ZK. There's been
some discussion in HBASE-1755 about actually moving META into ZK, but I think this jira is
a good step towards taking some of the complexity out of how we have to deal with catalog
tables everywhere.
> As-is, a new client already requires ZK to get the root location, so this would not change
those requirements in any way.
> The primary motivation for this is to simplify things like CatalogTracker. The way we
can handle root in that class is really simple but the tracking of meta is difficulty and
a bit hacky. This hack on tracking of the meta location is what caused one of the bugs over
in HBASE-3159.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira