[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645446#comment-14645446
]
Hadoop QA commented on HBASE-6721:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747704/HBASE-6721_11.patch
against master branch at commit 05de2ec5801fbba4577fb363f858a6e6f282c104.
ATTACHMENT ID: 12747704
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 30 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)
{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 6
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1908 checkstyle errors (more than the master's current 1864 errors).
{color:red}-1 InterfaceAudience{color}. The patch appears
to contain InterfaceAudience from hadoop rather than hbase:
+import org.apache.hadoop.classification.InterfaceAudience;
+import org.apache.hadoop.classification.InterfaceStability;
+import org.apache.hadoop.classification.InterfaceAudience;
+import org.apache.hadoop.classification.InterfaceAudience;.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the master's current 0 warnings).
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ * <code>rpc
getLastMajorCompactionTimestamp(.hbase.pb.MajorCompactionTimestampRequest)
returns (.hbase.pb.MajorCompactionTimestampResponse);</code>
+ * <code>rpc
getLastMajorCompactionTimestampForRegion(.hbase.pb.MajorCompactionTimestampForRegionRequest)
returns (.hbase.pb.MajorCompactionTimestampResponse);</code>
+ * <code>rpc getProcedureResult(.hbase.pb.GetProcedureResultRequest)
returns (.hbase.pb.GetProcedureResultResponse);</code>
+ * <code>rpc GetGroupInfo(.hbase.pb.GetGroupInfoRequest) returns
(.hbase.pb.GetGroupInfoResponse);</code>
+ * <code>rpc GetGroupInfoOfTable(.hbase.pb.GetGroupInfoOfTableRequest)
returns (.hbase.pb.GetGroupInfoOfTableResponse);</code>
+ * <code>rpc GetGroupInfoOfServer(.hbase.pb.GetGroupInfoOfServerRequest)
returns (.hbase.pb.GetGroupInfoOfServerResponse);</code>
+ * <code>rpc MoveServers(.hbase.pb.MoveServersRequest) returns
(.hbase.pb.MoveServersResponse);</code>
+ * <code>rpc MoveTables(.hbase.pb.MoveTablesRequest) returns
(.hbase.pb.MoveTablesResponse);</code>
+ * <code>rpc RemoveGroup(.hbase.pb.RemoveGroupRequest) returns
(.hbase.pb.RemoveGroupResponse);</code>
+ * <code>rpc BalanceGroup(.hbase.pb.BalanceGroupRequest) returns
(.hbase.pb.BalanceGroupResponse);</code>
{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:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14922//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14922//artifact/patchprocess/patchReleaseAuditWarnings.txt
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14922//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14922//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14922//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14922//console
This message is automatically generated.
> RegionServer Group based Assignment
> -----------------------------------
>
> Key: HBASE-6721
> URL: https://issues.apache.org/jira/browse/HBASE-6721
> Project: HBase
> Issue Type: New Feature
> Reporter: Francis Liu
> Assignee: Francis Liu
> Attachments: 6721-master-webUI.patch, HBASE-6721-DesigDoc.pdf,
> HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf,
> HBASE-6721_10.patch, HBASE-6721_11.patch, HBASE-6721_8.patch,
> HBASE-6721_9.patch, HBASE-6721_9.patch, HBASE-6721_94.patch,
> HBASE-6721_94.patch, HBASE-6721_94_2.patch, HBASE-6721_94_3.patch,
> HBASE-6721_94_3.patch, HBASE-6721_94_4.patch, HBASE-6721_94_5.patch,
> HBASE-6721_94_6.patch, HBASE-6721_94_7.patch, HBASE-6721_trunk.patch,
> HBASE-6721_trunk.patch, HBASE-6721_trunk.patch, HBASE-6721_trunk1.patch,
> HBASE-6721_trunk2.patch
>
>
> In multi-tenant deployments of HBase, it is likely that a RegionServer will
> be serving out regions from a number of different tables owned by various
> client applications. Being able to group a subset of running RegionServers
> and assign specific tables to it, provides a client application a level of
> isolation and resource allocation.
> The proposal essentially is to have an AssignmentManager which is aware of
> RegionServer groups and assigns tables to region servers based on groupings.
> Load balancing will occur on a per group basis as well.
> This is essentially a simplification of the approach taken in HBASE-4120. See
> attached document.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
