Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Caused by: org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.DoNotRetryIOException): org.apache.hadoop.hbase.DoNotRetryIOException: SCH.MYDELETE: Didn't find expected key values for table row in metadata row at org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:92) at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.createTable(MetaDataEndpointImpl.java:1614) at org.apache.phoenix.coprocessor.generated.MetaDataProtos$MetaDataService.callMethod(MetaDataProtos.java:16282) at org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:6082) at org.apache.hadoop.hbase.regionserver.HRegionServer.execServiceOnRegion(HRegionServer.java:3533) at org.apache.hadoop.hbase.regionserver.HRegionServer.execService(HRegionServer.java:3515) at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32496) at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2195) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:104) 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:722) Caused by: java.lang.IllegalStateException: Didn't find expected key values for table row in metadata row at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.getTable(MetaDataEndpointImpl.java:874) at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.buildTable(MetaDataEndpointImpl.java:563) at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.loadTable(MetaDataEndpointImpl.java:1264) at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.createTable(MetaDataEndpointImpl.java:1443)
Steps
- Create and drop table with 4.9 client/4.x server
create table sch.mydelete (pk1 varchar not null primary key, mycol varchar) salt_buckets=4; drop table sch.mydelete; - Exception on creating table again with 4.x client/server.
Attachments
Attachments
Issue Links
- is broken by
-
PHOENIX-2051 Link record is in the format CHILD-PARENT for phoenix views and it has to scan the entire table to find the parent suffix.
- Resolved