[
https://issues.apache.org/jira/browse/HBASE-14456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901952#comment-14901952
]
Hadoop QA commented on HBASE-14456:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12761548/HBASE-14456_v2.patch
against master branch at commit 783e20e1a7ca2c796b8d9c9e938e5c5779aa30c7.
ATTACHMENT ID: 12761548
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 90 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0 2.7.1)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 5
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1824 checkstyle errors (more than the master's current 1823 errors).
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList$Generator.jobCompletion(IntegrationTestBigLinkedList.java:611)
at
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList$Generator.runRandomInputGenerator(IntegrationTestBigLinkedList.java:568)
at
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList$Generator.run(IntegrationTestBigLinkedList.java:621)
at
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList$Loop.runGenerator(IntegrationTestBigLinkedList.java:1245)
at
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList$Loop.run(IntegrationTestBigLinkedList.java:1295)
at
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList.testContinuousIngest(IntegrationTestBigLinkedList.java:1584)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15659//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15659//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15659//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15659//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15659//console
This message is automatically generated.
> Implement a namespace-based region grouping strategy for
> RegionGroupingProvider
> -------------------------------------------------------------------------------
>
> Key: HBASE-14456
> URL: https://issues.apache.org/jira/browse/HBASE-14456
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 2.0.0, 1.3.0
> Reporter: Yu Li
> Assignee: Yu Li
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-14456.patch, HBASE-14456_v2.patch
>
>
> In HBASE-5699 we introduced multiple wal, and after some succeeding works we
> now have two main kinds of wal providers: DefaultWALProvider and
> RegionGroupingProvider, while DefaultWALProvider supplies a _single_ wal per
> regionserver, RegionGroupingProvider supplies _multiple_ wals according to
> the RegionGroupingStrategy it's using.
> Now there're two kinds of RegionGroupingStrategy: _identity_ and _bounded_,
> in which "identity" only for testing (trial) purpose and "bounded" for
> randomly assigning region writes to bounded number of wals. Although the
> "bounded" strategy is good enough for IO leverage, we may still want a more
> "designed" way to distribute the region writes, like having one wal group per
> business.
> Since we already have namespace for multi-tenancy, it would be good to have
> namespace-based grouping strategy, and this is exactly what this JIRA is for.
> There might be more benefits if we have namespace-based wal group, like only
> replicating data for the namespace in need w/o filtering anything useless, or
> only force region flush for the heavy loaded namespace, etc. although we
> won't include all these in this single JIRA.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
