You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Jinrui Zhang (Jira)" <ji...@apache.org> on 2022/10/19 09:16:00 UTC

[jira] [Commented] (IOTDB-4671) [ MultiLeaderConsensus ] snapshot is not deleted after load snapshot

    [ https://issues.apache.org/jira/browse/IOTDB-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620134#comment-17620134 ] 

Jinrui Zhang commented on IOTDB-4671:
-------------------------------------

Currently the implementation doesn't delete the snapshot after loading. So it is by design. 

 

And I will add the remove logic later

> [ MultiLeaderConsensus ] snapshot is not deleted after load snapshot
> --------------------------------------------------------------------
>
>                 Key: IOTDB-4671
>                 URL: https://issues.apache.org/jira/browse/IOTDB-4671
>             Project: Apache IoTDB
>          Issue Type: Improvement
>          Components: mpp-cluster
>            Reporter: 刘珍
>            Assignee: Jinrui Zhang
>            Priority: Major
>         Attachments: image-2022-10-17-16-55-13-402.png, more_dev.conf
>
>
> master_1013_00dc222
> schema : ratis
> data : MultiLeaderConsensus  
> 3副本,3C5D , 缩容1个节点(ip72)
> new peer   load snapshot 后,迁移过来的dataregion中的snapshot 没有删除。
> ip73 共识层的文件信息:
>  !image-2022-10-17-16-55-13-402.png! 
> 测试环境:
> 测试环境
> 1. 启动3C5D 48CPU 384GB
> 3C : 192.168.10.72 , 73, 74
> 5D : 192.168.10.72 , 73, 74 , 75,76
> 配置参数
> 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
> connection_timeout_ms=120000
> DataNode
> MAX_HEAP_SIZE="256G"
> MAX_DIRECT_MEMORY_SIZE="32G"
> connection_timeout_ms=120000
> max_connection_for_internal_service=200
> max_waiting_time_when_insert_blocked=600000
> query_timeout_threshold=36000000
> enable_auto_create_schema=false
> 2. bm 运行配置见附件
> 3. 等待3小时后执行delete timeseries root.**
> 脚本在ip72 ${iotdb_dir}/datanode下
> cat rm_dn.sh 
> #!/bin/bash
> sleep 3h
> ./sbin/start-cli.sh -h 192.168.10.74 -e "show regions"
> ./sbin/start-cli.sh -h 192.168.10.74 -e "show cluster"
> ./sbin/start-cli.sh -h 192.168.10.74 -e "delete timeseries root.**" &
> sleep 120
> ./sbin/remove-datanode.sh  "192.168.10.72:6667"  > 1014_remove_ip72.out
> 缩容成功后,查看ip73的data/consensus/data_region下的文件信息。



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