刘珍 created IOTDB-5016:
-------------------------
Summary: Remove datanode : The consensus group SchemaRegion[8]
doesn't exist
Key: IOTDB-5016
URL: https://issues.apache.org/jira/browse/IOTDB-5016
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: 刘珍
Assignee: Song Ziyang
master_1119_fd57958
1. start 3rep 3C5D cluster
2. Benchmark write data
3. Remove ip72 datanode after 40 minutes
4. ip72 datanode removed successfully.
5. rm -rf ip72 datanode's data ，ip72 datanode rejoining the Cluster
6. Remove ip68 datanode
ip62 datanode ERROR ：
2022-11-21 00:27:30,145
[pool-21-IoTDB-MPPCoordinator-16$20221120_162730_39857_3.1.0] ERROR
o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:160 - Execute FragmentInstance
failed: The consensus group SchemaRegion[8] doesn't exist
2022-11-21 00:27:30,232
[pool-25-IoTDB-ClientRPC-Processor-1$20221120_162730_39856_3] ERROR
o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:123 - [DispatchFailed]
java.lang.RuntimeException: {color:#FF8B00}*cannot fetch schema, status is:
301, msg is: Execute FragmentInstance failed: The consensus group
SchemaRegion[8] doesn't exist*{color}
at
org.apache.iotdb.db.mpp.plan.analyze.ClusterSchemaFetcher.executeSchemaFetchQuery(ClusterSchemaFetcher.java:188)
at
org.apache.iotdb.db.mpp.plan.analyze.ClusterSchemaFetcher.fetchSchema(ClusterSchemaFetcher.java:156)
at
org.apache.iotdb.db.mpp.plan.analyze.ClusterSchemaFetcher.fetchSchema(ClusterSchemaFetcher.java:98)
at
org.apache.iotdb.db.mpp.plan.analyze.ClusterSchemaFetcher.fetchSchemaWithAutoCreate(ClusterSchemaFetcher.java:265)
at
org.apache.iotdb.db.mpp.plan.analyze.SchemaValidator.validate(SchemaValidator.java:56)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.executeDataInsert(RegionWriteExecutor.java:193)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitInsertTablet(RegionWriteExecutor.java:165)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitInsertTablet(RegionWriteExecutor.java:119)
at
org.apache.iotdb.db.mpp.plan.planner.plan.node.write.InsertTabletNode.accept(InsertTabletNode.java:1086)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor.execute(RegionWriteExecutor.java:85)
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:288)
at
org.apache.iotdb.db.mpp.plan.execution.QueryExecution.start(QueryExecution.java:206)
at
org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:150)
at
org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:164)
at
org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.insertTablet(ClientRPCServiceImpl.java:1234)
at
org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$insertTablet.getResult(IClientRPCService.java:4078)
at
org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$insertTablet.getResult(IClientRPCService.java:4058)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at
org.apache.iotdb.db.service.thrift.ProcessorWithMetrics.process(ProcessorWithMetrics.java:64)
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)
测试环境
1. 3C 192.168.10.62 /66 /68 72C256GB
5D 192.168.10.62 /66 /68 72C256GB
192.168.10.72、73 48C384GB
配置文件
ConfigNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
