You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "kangkang.guo (Jira)" <ji...@apache.org> on 2020/03/27 11:11:00 UTC
[jira] [Updated] (HBASE-24067) [RSGroup] Error logs appear when the
table is created
[ https://issues.apache.org/jira/browse/HBASE-24067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
kangkang.guo updated HBASE-24067:
---------------------------------
Description:
Will create table assigned to the corresponding rsgroup, appear TableStateNotFoundException.
This doesn't seem to cause any problems, but I think it's best to avoid error logs like this
was:
Will create table assigned to the corresponding rsgroup, appear TableStateNotFoundException:
2020-03-27 15:49:21,959 INFO [RpcServer.default.RWQ.Fifo.read.handler=139,queue=14,port=16000] rsgroup.RSGroupAdminServer: Moving table Test:t3 to RSGroup default
2020-03-27 15:49:21,971 ERROR [RpcServer.default.RWQ.Fifo.read.handler=139,queue=14,port=16000] master.TableStateManager: Unable to get table Test:t3 state
org.apache.hadoop.hbase.master.TableStateManager$TableStateNotFoundException: Test:t3
at org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:215)
at org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:147)
at org.apache.hadoop.hbase.master.assignment.AssignmentManager.isTableDisabled(AssignmentManager.java:388)
at org.apache.hadoop.hbase.rsgroup.RSGroupAdminServer.moveTableRegionsToGroup(RSGroupAdminServer.java:252)
at org.apache.hadoop.hbase.rsgroup.RSGroupAdminServer.moveTables(RSGroupAdminServer.java:366)
at org.apache.hadoop.hbase.rsgroup.RSGroupAdminEndpoint.assignTableToGroup(RSGroupAdminEndpoint.java:447)
at org.apache.hadoop.hbase.rsgroup.RSGroupAdminEndpoint.postCreateTable(RSGroupAdminEndpoint.java:470)
at org.apache.hadoop.hbase.master.MasterCoprocessorHost$13.call(MasterCoprocessorHost.java:350)
at org.apache.hadoop.hbase.master.MasterCoprocessorHost$13.call(MasterCoprocessorHost.java:347)
at org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithoutResult.callObserver(CoprocessorHost.java:551)
at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:625)
at org.apache.hadoop.hbase.master.MasterCoprocessorHost.postCreateTable(MasterCoprocessorHost.java:347)
at org.apache.hadoop.hbase.master.HMaster$4.run(HMaster.java:2043)
at org.apache.hadoop.hbase.master.procedure.MasterProcedureUtil.submitProcedure(MasterProcedureUtil.java:134)
at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:2026)
at org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:659)
at org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:133)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318)
2020-03-27 15:49:21,971 INFO [RpcServer.default.RWQ.Fifo.read.handler=139,queue=14,port=16000] rsgroup.RSGroupAdminServer: Moving region(s) for table Test:t3 to RSGroup default
2020-03-27 15:49:21,972 INFO [RpcServer.default.RWQ.Fifo.read.handler=139,queue=14,port=16000] master.MasterRpcServices: Client=hbase//**.**.**.** procedure request for creating table: namespace: "Test"
qualifier: "t3"
> [RSGroup] Error logs appear when the table is created
> -----------------------------------------------------
>
> Key: HBASE-24067
> URL: https://issues.apache.org/jira/browse/HBASE-24067
> Project: HBase
> Issue Type: Improvement
> Components: rsgroup
> Affects Versions: 2.1.7, 2.1.8, 2.2.3, 2.2.4
> Reporter: kangkang.guo
> Assignee: kangkang.guo
> Priority: Minor
>
> Will create table assigned to the corresponding rsgroup, appear TableStateNotFoundException.
> This doesn't seem to cause any problems, but I think it's best to avoid error logs like this
--
This message was sent by Atlassian Jira
(v8.3.4#803005)