You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "刘珍 (Jira)" <ji...@apache.org> on 2022/11/01 07:19:00 UTC
[jira] [Created] (IOTDB-4823) [ delete storage group root.** ] The corresponding path and tsfile are not deleted
刘珍 created IOTDB-4823:
-------------------------
Summary: [ delete storage group root.** ] The corresponding path and tsfile are not deleted
Key: IOTDB-4823
URL: https://issues.apache.org/jira/browse/IOTDB-4823
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: 刘珍
Assignee: Gaofei Cao
Attachments: image-2022-11-01-15-16-55-472.png
master_1101_bc0e88b
3rep ， 3C3D
schema region : ratis
data region : multiLeader
delete storage group root.**
The corresponding path and tsfile are not deleted :
!image-2022-11-01-15-16-55-472.png!
ConfigNode leader (ip62) warn :
2022-11-01 14:58:25,186 [ProcExecWorker-10] WARN o.a.i.c.c.s.SyncDataNodeClientPool:104 -{color:#DE350B}* INVALIDATE_SCHEMA_CACHE failed on *{color}DataNode TEndPoint(ip:192.168.10.62, port:9003), because Error in calling method invalidateSchemaCache, retrying 0...
2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck ProcExecWorker-9(pid=9), run time 24559 ms
2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck ProcExecWorker-10(pid=10), run time 24558 ms
2022-11-01 14:58:29,609 [ProcedureWorkerThreadMonitor] WARN o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck ProcExecWorker-11(pid=11), run time 24548 ms
2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck ProcExecWorker-9(pid=9), run time 29560 ms
2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck ProcExecWorker-10(pid=10), run time 29559 ms
2022-11-01 14:58:34,610 [ProcedureWorkerThreadMonitor] WARN o.a.i.c.p.ProcedureExecutor$WorkerMonitor:811 - Worker stuck ProcExecWorker-11(pid=11), run time 29549 ms
2022-11-01 14:58:37,869 [ProcExecWorker-13] WARN o.a.i.c.m.ClusterSchemaManager:333 - {color:#DE350B}*Adjust maxRegionGroupCount failed because StorageGroup doesn't exist*{color}
org.apache.iotdb.confignode.exception.StorageGroupNotExistsException: StorageGroup: root.test.g_0 doesn't exist.
at org.apache.iotdb.confignode.persistence.partition.PartitionInfo.getRegionCount(PartitionInfo.java:620)
at org.apache.iotdb.confignode.manager.partition.PartitionManager.getRegionCount(PartitionManager.java:483)
at org.apache.iotdb.confignode.manager.ClusterSchemaManager.adjustMaxRegionGroupCount(ClusterSchemaManager.java:299)
at org.apache.iotdb.confignode.manager.ClusterSchemaManager.deleteStorageGroup(ClusterSchemaManager.java:145)
at org.apache.iotdb.confignode.procedure.env.ConfigNodeProcedureEnv.deleteConfig(ConfigNodeProcedureEnv.java:125)
at org.apache.iotdb.confignode.procedure.impl.schema.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:122)
at org.apache.iotdb.confignode.procedure.impl.schema.DeleteStorageGroupProcedure.executeFromState(DeleteStorageGroupProcedure.java:48)
at org.apache.iotdb.confignode.procedure.impl.statemachine.StateMachineProcedure.execute(StateMachineProcedure.java:186)
at org.apache.iotdb.confignode.procedure.Procedure.doExecute(Procedure.java:365)
at org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:414)
at org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:373)
at org.apache.iotdb.confignode.procedure.ProcedureExecutor.access$300(ProcedureExecutor.java:50)
at org.apache.iotdb.confignode.procedure.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:741)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)