[jira] [Created] (IOTDB-4744) [DispatchFailed] java.lang.IndexOutOfBoundsException: Index: 3, Size: 3

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

刘珍 created IOTDB-4744:
-------------------------

             Summary: [DispatchFailed]  java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
                 Key: IOTDB-4744
                 URL: https://issues.apache.org/jira/browse/IOTDB-4744
             Project: Apache IoTDB
          Issue Type: Bug
          Components: mpp-cluster
    Affects Versions: 0.14.0-SNAPSHOT
            Reporter: 刘珍
            Assignee: Jinrui Zhang


master_1023_2fea011
schema region : ratis
data region : multiLeader

3rep , 3C3D . 
benchmark：
IS_DELETE_DATA=false
CREATE_SCHEMA=true

benchmark runs the metadata creation operation twice, (ip62） datanode ERROR LOG :
2022-10-25 09:53:12,210 [pool-26-IoTDB-ClientRPC-Processor-8$20221025_015312_00103_3] {color:#DE350B}*ERROR o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:123 - [DispatchFailed]
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3*{color}
        at java.util.ArrayList.rangeCheck(ArrayList.java:659)
        at java.util.ArrayList.remove(ArrayList.java:498)
        at org.apache.iotdb.db.mpp.plan.planner.plan.node.metedata.write.MeasurementGroup.removeMeasurement(MeasurementGroup.java:122)
        at org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitCreateMultiTimeSeries(RegionWriteExecutor.java:349)
        at org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitCreateMultiTimeSeries(RegionWriteExecutor.java:113)
        at org.apache.iotdb.db.mpp.plan.planner.plan.node.metedata.write.CreateMultiTimeSeriesNode.accept(CreateMultiTimeSeriesNode.java:141)
        at org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor.execute(RegionWriteExecutor.java:79)
        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:102)
        at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.schedule(QueryExecution.java:277)
        at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.start(QueryExecution.java:195)
        at org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:146)
        at org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:160)
        at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.createMultiTimeseries(ClientRPCServiceImpl.java:467)
        at org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$createMultiTimeseries.getResult(IClientRPCService.java:3387)
        at org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$createMultiTimeseries.getResult(IClientRPCService.java:3367)
        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)

Test environment ：
1. 192.168.10.62 / 66 /68 72CPU 256GB
benchmark : ip64 /data/liuzhen_test/weektest/benchmark_tool

ConfigNode
MAX_HEAP_SIZE="8G"
schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
data_region_consensus_protocol_class=org.apache.iotdb.consensus.multileader.MultiLeaderConsensus
schema_replication_factor=3
data_replication_factor=3
partition_region_ratis_request_timeout_ms = 1200000
schema_region_ratis_request_timeout_ms = 1200000
data_region_ratis_request_timeout_ms = 1200000
partition_region_ratis_max_retry_attempts = 1
schema_region_ratis_max_retry_attempts = 1
data_region_ratis_max_retry_attempts = 1

DataNode
MAX_HEAP_SIZE="192G"
MAX_DIRECT_MEMORY_SIZE="32G"
query_timeout_threshold=36000000

2. benchmark configuration
see attachment .
Run twice

3. View ip62 datanode logs



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