hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6721) RegionServer Group based Assignment
Date Mon, 14 Dec 2015 20:01:47 GMT

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

Ted Yu commented on HBASE-6721:
-------------------------------

Francis:
You can copy the following file from branch-1.1 to master branch so that you can run TestShell:
hbase-shell/src/test/java/org/apache/hadoop/hbase/client/TestShell.java

I ran TestShell locally and still got:
{code}
test_Test_Basic_Group_Commands(Hbase::GroupShellTest):
NativeException: org.apache.hadoop.hbase.exceptions.UnknownProtocolException: org.apache.hadoop.hbase.exceptions.UnknownProtocolException:
No registered master coprocessor    service found for name hbase.pb.GroupAdminService
  at org.apache.hadoop.hbase.master.MasterRpcServices.execMasterService(MasterRpcServices.java:682)
  at org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:57964)
  at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2213)
  at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:109)
  at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
  at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
  at java.lang.Thread.run(Thread.java:745)

    sun/reflect/NativeConstructorAccessorImpl.java:-2:in `newInstance0'
    sun/reflect/NativeConstructorAccessorImpl.java:57:in `newInstance'
    sun/reflect/DelegatingConstructorAccessorImpl.java:45:in `newInstance'
    java/lang/reflect/Constructor.java:526:in `newInstance'
    org/apache/hadoop/ipc/RemoteException.java:106:in `instantiateException'
    org/apache/hadoop/ipc/RemoteException.java:95:in `unwrapRemoteException'
    org/apache/hadoop/hbase/ipc/AsyncCall.java:127:in `setFailed'
    org/apache/hadoop/hbase/ipc/AsyncServerResponseHandler.java:83:in `channelRead'
    io/netty/channel/AbstractChannelHandlerContext.java:308:in `invokeChannelRead'
    io/netty/channel/AbstractChannelHandlerContext.java:294:in `fireChannelRead'
    io/netty/handler/codec/ByteToMessageDecoder.java:244:in `channelRead'
    io/netty/channel/AbstractChannelHandlerContext.java:308:in `invokeChannelRead'
    io/netty/channel/AbstractChannelHandlerContext.java:294:in `fireChannelRead'
    io/netty/channel/DefaultChannelPipeline.java:846:in `fireChannelRead'
    io/netty/channel/nio/AbstractNioByteChannel.java:131:in `read'
    io/netty/channel/nio/NioEventLoop.java:511:in `processSelectedKey'
    io/netty/channel/nio/NioEventLoop.java:468:in `processSelectedKeysOptimized'
    io/netty/channel/nio/NioEventLoop.java:382:in `processSelectedKeys'
    io/netty/channel/nio/NioEventLoop.java:354:in `run'
    io/netty/util/concurrent/SingleThreadEventExecutor.java:110:in `run'
    java/lang/Thread.java:745:in `run'
    ./src/test/ruby/shell/group_shell_test.rb:43:in `test_Test_Basic_Group_Commands'
    org/jruby/RubyProc.java:270:in `call'
    org/jruby/RubyKernel.java:2105:in `send'
    org/jruby/RubyArray.java:1620:in `each'
    org/jruby/RubyArray.java:1620:in `each'

  2) Failure:
test_Test_bogus_arguments(Hbase::GroupShellTest)
    [./src/test/ruby/shell/group_shell_test.rb:85:in `test_Test_bogus_arguments'
     org/jruby/RubyProc.java:270:in `call'
     org/jruby/RubyKernel.java:2105:in `send'
     org/jruby/RubyArray.java:1620:in `each'
     org/jruby/RubyArray.java:1620:in `each']:
<ArgumentError> exception expected but was
Class: <NativeException>
Message: <"org.apache.hadoop.hbase.exceptions.UnknownProtocolException: org.apache.hadoop.hbase.exceptions.UnknownProtocolException:
No registered master coprocessor service  found for name hbase.pb.GroupAdminService\n\tat
org.apache.hadoop.hbase.master.MasterRpcServices.execMasterService(MasterRpcServices.java:682)\n\tat
org.apache.hadoop.hbase.  protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:57964)\n\tat
org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2213)\n\tat org.   apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:109)\n\tat
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)\n\tat org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)\n\tat
java.lang.Thread.run(Thread.java:745)\n">
{code}

> 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
>              Labels: hbase-6721
>         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_12.patch, HBASE-6721_13.patch,
HBASE-6721_14.patch, HBASE-6721_15.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_hbase-6721_addendum.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, hbase-6721-v15-branch-1.1.patch, hbase-6721-v16.patch,
hbase-6721-v17.patch, hbase-6721-v18.patch, hbase-6721-v19.patch, 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)

Mime
View raw message