[
https://issues.apache.org/jira/browse/PHOENIX-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255298#comment-17255298
]
Viraj Jasani commented on PHOENIX-6104:
---------------------------------------
Disable table followed by enable table (which is present in test for quite some
time) is not recommended practice if we want to split a table synchronously,
but good to get 100% confirmation on this, I might be wrong :)
Moreover, I believe we have another issue, when I looked at the actual
splitting of SYSTEM.CATALOG, it doesn't seem to be happening with small no of
entries. If you just try to comment out admin.disableTable() and
admin.enableTable() calls, the test init itself will fail with:
{code:java}
org.apache.hadoop.hbase.client.DoNotRetryRegionException:
org.apache.hadoop.hbase.client.DoNotRetryRegionException:
0ee21233d2901e3a2ab4d982cb162c97 is not OPEN;
regionState={0ee21233d2901e3a2ab4d982cb162c97 state=SPLITTING,
ts=1609093201137,
server=192.168.0.104,65115,1609093180149}org.apache.hadoop.hbase.client.DoNotRetryRegionException:
org.apache.hadoop.hbase.client.DoNotRetryRegionException:
0ee21233d2901e3a2ab4d982cb162c97 is not OPEN;
regionState={0ee21233d2901e3a2ab4d982cb162c97 state=SPLITTING,
ts=1609093201137, server=192.168.0.104,65115,1609093180149} at
org.apache.hadoop.hbase.master.procedure.AbstractStateMachineTableProcedure.checkOnline(AbstractStateMachineTableProcedure.java:194)
at
org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.<init>(SplitTableRegionProcedure.java:115)
at
org.apache.hadoop.hbase.master.assignment.AssignmentManager.createSplitProcedure(AssignmentManager.java:754)
at org.apache.hadoop.hbase.master.HMaster$3.run(HMaster.java:1869) at
org.apache.hadoop.hbase.master.procedure.MasterProcedureUtil.submitProcedure(MasterProcedureUtil.java:134)
at org.apache.hadoop.hbase.master.HMaster.splitRegion(HMaster.java:1861) at
org.apache.hadoop.hbase.master.MasterRpcServices.splitRegion(MasterRpcServices.java:818)
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:324) at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304) at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.instantiateException(RemoteWithExtrasException.java:99)
at
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.unwrapRemoteException(RemoteWithExtrasException.java:89)
at
org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.makeIOExceptionOfException(ProtobufUtil.java:362)
at
org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.handleRemoteException(ProtobufUtil.java:350)
at org.apache.hadoop.hbase.client.MasterCallable.call(MasterCallable.java:101)
at
org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:107)
at
org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:3070)
at
org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:3062)
at
org.apache.hadoop.hbase.client.HBaseAdmin.splitRegionAsync(HBaseAdmin.java:1819)
at org.apache.hadoop.hbase.client.HBaseAdmin.split(HBaseAdmin.java:1884) at
org.apache.phoenix.query.BaseTest.splitRegion(BaseTest.java:1836) at
org.apache.phoenix.query.BaseTest.splitTable(BaseTest.java:1870) at
org.apache.phoenix.query.BaseTest.splitSystemCatalog(BaseTest.java:1942) at
org.apache.phoenix.end2end.SplitSystemCatalogIT.splitSystemCatalog(SplitSystemCatalogIT.java:87)
at
org.apache.phoenix.end2end.SplitSystemCatalogIT.doSetup(SplitSystemCatalogIT.java:68)
{code}
Table doesn't seem to have enough entries to make it worth splittable.
The above logs belong to default hbase profile 2.1 based test.
> SplitSystemCatalogIT tests very unstable with Hbase 2.3
> -------------------------------------------------------
>
> Key: PHOENIX-6104
> URL: https://issues.apache.org/jira/browse/PHOENIX-6104
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Attachments: 6104-testouput.log
>
>
> The failure is in the test preparation code, where we split the system
> catalog table, and it seems to be a HBase issue, rather than a Phoenix one,
> but we need to track the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
