[jira] [Created] (IOTDB-4918) drop a timeseries of an aligned device, and recreate again, Msg: 500: Unexpected errors: null

["changxue (Jira)" <ji...@apache.org>]

changxue created IOTDB-4918:
-------------------------------

             Summary: drop a timeseries of an aligned device, and recreate again,  Msg: 500: Unexpected errors: null 
                 Key: IOTDB-4918
                 URL: https://issues.apache.org/jira/browse/IOTDB-4918
             Project: Apache IoTDB
          Issue Type: Bug
          Components: Core/Server
    Affects Versions: 0.14.0-SNAPSHOT
            Reporter: changxue
            Assignee: Haonan Hou


drop a timeseries of an aligned device, and recreate again, Msg: 500: Unexpected errors: null 

 

environment:

3C3D cluster, Nov.11 master source codes

 

reproduction:
{code:java}
CREATE ALIGNED TIMESERIES root.udf.d2 (s1 int64, s2 int64, s3 int64);
delete timeseries root.udf.d2.s1;
CREATE ALIGNED TIMESERIES root.udf.d2 (s1 int3264, s2 int64, s3 int64);
Msg: 500: Unexpected errors: null {code}
datanode log:
{code:java}
2022-11-11 19:09:37,255 [pool-25-IoTDB-ClientRPC-Processor-7$20221111_110937_01101_1.1.0] ERROR o.a.i.d.m.e.e.RegionWriteExecutor$WritePlanNodeExecutionVisitor:313 - Metadata error:  
2022-11-11 19:09:37,256 [pool-25-IoTDB-ClientRPC-Processor-7$20221111_110937_01101_1] ERROR o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:123 - [DispatchFailed] 
java.lang.NullPointerException: null
    at org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitCreateAlignedTimeSeries(RegionWriteExecutor.java:316)
    at org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitCreateAlignedTimeSeries(RegionWriteExecutor.java:118)
    at org.apache.iotdb.db.mpp.plan.planner.plan.node.metedata.write.CreateAlignedTimeSeriesNode.accept(CreateAlignedTimeSeriesNode.java:191)
    at org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor.execute(RegionWriteExecutor.java:84)
    at org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchLocally(FragmentInstanceDispatcherImpl.java:232)
    at org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchOneInstance(FragmentInstanceDispatcherImpl.java:137)
    at org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchWriteSync(FragmentInstanceDispatcherImpl.java:119)
    at org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatch(FragmentInstanceDispatcherImpl.java:90)
    at org.apache.iotdb.db.mpp.plan.scheduler.ClusterScheduler.start(ClusterScheduler.java:106)
    at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.schedule(QueryExecution.java:287)
    at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.start(QueryExecution.java:205)
    at org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:150)
    at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementInternal(ClientRPCServiceImpl.java:215)
    at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementV2(ClientRPCServiceImpl.java:390)
    at org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3453)
    at org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3433)
    at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
    at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
    at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748){code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)