hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14456) Implement a namespace-based region grouping strategy for RegionGroupingProvider
Date Thu, 24 Sep 2015 20:33:04 GMT

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

Hadoop QA commented on HBASE-14456:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against branch-1 branch at commit 5b7894f92ba3e9ff700da1e9194ebb4774d8b71e.
  ATTACHMENT ID: 12762180

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 87 new or modified

    {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:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle 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:red}-1 core tests{color}.  The patch failed these unit tests:

     {color:red}-1 core zombie tests{color}.  There are 6 zombie test(s): 

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15722//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15722//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15722//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15722//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.branch-1.patch, HBASE-14456.branch-1.v2.patch, HBASE-14456.patch,
HBASE-14456_v2.patch, HBASE-14456_v3.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

View raw message