[
https://issues.apache.org/jira/browse/IOTDB-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634676#comment-17634676
]
Gaofei Cao commented on IOTDB-4823:
-----------------------------------
*{color:#de350b}1) The corresponding path and tsfile are not deleted :
【Success test in local】
{color}*
*{color:#de350b}!image-2022-11-16-14-26-04-326.png|width=379,height=642!!image-2022-11-16-14-26-40-379.png|width=498,height=500!{color}*
{*}{color:#de350b}2）INVALIDATE_SCHEMA_CACHE failed on *{color}DataNode
TEndPoint(ip:192.168.10.62, port:9003), because Error in calling method
invalidateSchemaCache, retrying 0... 【Can not reappear in local】{*}{*}{*}
*3）Adjust maxRegionGroupCount failed because StorageGroup doesn't
exist{color:#FF0000}【Fixed】{color}*
> [ 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: 伊丹翔
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-11-01-15-16-55-472.png,
> image-2022-11-16-14-26-04-326.png, image-2022-11-16-14-26-40-379.png,
> iotdb_4823.conf
>
>
> 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（Fixed）*{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)
> 测试流程：
> 1. 192.168.10.62/66/68 72C256GB
> ConfigNode
> MAX_HEAP_SIZE="8G"
> Common
> query_timeout_threshold=36000000
> 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"
> 2. bm 在192.168.10.64
> /data/liuzhen_test/weektest/benchmark_tool
> 配置见附件
> 3. bm 运行完成，数据同步完成，正常停止ip68的datanode
> 4. 清ip68 OS 缓存 ，启动ip68 的 datanode
> 5. ip62 cli -e "delete storage group root.**"
> 查看各节点的consensus和data下的region信息
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
