[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697919#comment-14697919
]
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/12750586/HBASE-6721_0.98_2.patch
against 0.98 branch at commit 45aafb25b7911b5917ab47133e3e4268806e4c91.
ATTACHMENT ID: 12750586
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 33 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
28 warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
3913 checkstyle errors (more than the master's current 3876 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:
+ public GetGroupInfoResponse getGroupInfo(RpcController controller,
GetGroupInfoRequest request) throws ServiceException {
+ public GetGroupInfoOfTableResponse getGroupInfoOfTable(RpcController
controller, GetGroupInfoOfTableRequest request) throws ServiceException {
+ public GetGroupInfoOfServerResponse getGroupInfoOfServer(RpcController
controller, GetGroupInfoOfServerRequest request) throws ServiceException {
+ public MoveServersResponse moveServers(RpcController controller,
MoveServersRequest request) throws ServiceException {
+ public MoveTablesResponse moveTables(RpcController controller,
MoveTablesRequest request) throws ServiceException {
+ public AddGroupResponse addGroup(RpcController controller,
AddGroupRequest request) throws ServiceException {
+ public RemoveGroupResponse removeGroup(RpcController controller,
RemoveGroupRequest request) throws ServiceException {
+ public BalanceGroupResponse balanceGroup(RpcController controller,
BalanceGroupRequest request) throws ServiceException {
+ public ListGroupInfosResponse listGroupInfos(RpcController controller,
ListGroupInfosRequest request) throws ServiceException {
+ * <code>rpc GetGroupInfoOfTable(.GetGroupInfoOfTableRequest) returns
(.GetGroupInfoOfTableResponse);</code>
{color:red}-1 site{color}. The patch appears to cause mvn post-site goal
to fail.
{color:green}+1 core tests{color}. The patch passed unit tests in .
{color:red}-1 core zombie tests{color}. There are 5 zombie test(s):
at
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.testLogRolling(TestLogRolling.java:219)
at
org.apache.hadoop.hbase.TestIOFencing.testFencingAroundCompaction(TestIOFencing.java:227)
at
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster.testRITStateForRollback(TestSplitTransactionOnCluster.java:292)
at
org.apache.hadoop.hbase.io.encoding.TestEncodedSeekers.testEncodedSeeker(TestEncodedSeekers.java:118)
at
org.apache.hadoop.hbase.TestClusterBootOrder.testBootRegionServerFirst(TestClusterBootOrder.java:104)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15105//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15105//artifact/patchprocess/patchReleaseAuditWarnings.txt
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15105//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15105//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15105//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15105//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
> GroupBasedLoadBalancer Sequence Diagram.xml, HBASE-6721-DesigDoc.pdf,
> HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf,
> HBASE-6721_0.98_2.patch, 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_98_1.patch, HBASE-6721_98_2.patch, HBASE-6721_trunk.patch,
> HBASE-6721_trunk.patch, HBASE-6721_trunk.patch, HBASE-6721_trunk1.patch,
> HBASE-6721_trunk2.patch, balanceCluster Sequence Diagram.svg,
> immediateAssignments Sequence Diagram.svg, randomAssignment Sequence
> Diagram.svg, retainAssignment Sequence Diagram.svg, roundRobinAssignment
> Sequence Diagram.svg
>
>
> 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)
