[
https://issues.apache.org/jira/browse/IOTDB-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17639889#comment-17639889
]
Jinrui Zhang commented on IOTDB-5045:
-------------------------------------
According to current investigation with [~Marcoss] , we found that some write
operation may happen even the DataRegion has been marked as deleted. The `write
operation` may be on going while the DataRegion is being deleted. And when the
DataRegion’s deletion is done, the ongoing write may trigger the DataRegion's
write again so that some wal/tsfile is generated.
There is no lock/concurrent control between `write` and `DataRegion delete`, so
this case may be triggered in many scenarios. If the delete is submitted
immediately after insertion, the SyncLog of IoTConsensus can trigger this case
easily when the total insert operation is less than 5.
What we should do next:
* Add the concurrent control between DataRegion's write and delete. Ensure the
write operation will be discards/rejected when the DataRegion has been marked
as deleted
> [delete] After running "drop database root.**", wal and tsfile still left
> ---------------------------------------------------------------------------
>
> Key: IOTDB-5045
> URL: https://issues.apache.org/jira/browse/IOTDB-5045
> Project: Apache IoTDB
> Issue Type: Bug
> Affects Versions: 0.14.0-SNAPSHOT
> Reporter: changxue
> Assignee: Yukun Zhou
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.0.0
>
> Attachments: allnodes-log.tar.gz, udf-privilege.run
>
>
> [delete] After running "drop database root.**", wal and tsfile left rather
> than cleanup
> 3C3D cluster, Nov.25 14:00 source codes
> reproduction:
> execute the statements of attchachment udf-privilege.run on start-cli.sh
> window several times
> actual result:
> They are all empty:
> show databases;
> show timeseries root.**;
> show regions;
> I've run flush in command wiindow but no use.
> But there are also tsfile and wal files left and won't be removed.
> find $IOTDB_HOME/data/datanode/data -type f | xargs ls -hl
> {code}
> -rw-r--r-- 1 atmos root 5 Nov 25 14:30
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/data/.iotdb-lock
> -rw-r--r-- 1 atmos root 0 Nov 25 14:43
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/data/sequence/root.sg1/10/0/1669358591044-1-0-0.tsfile
> -rw-r--r-- 1 atmos root 0 Nov 25 14:59
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/data/sequence/root.sg1/19/0/1669359549944-1-0-0.tsfile
> -rw-r--r-- 1 atmos root 0 Nov 25 14:59
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/data/sequence/root.sg1/25/0/1669359576659-1-0-0.tsfile
> -rw-r--r-- 1 atmos root 0 Nov 25 15:13
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/data/sequence/root.sg1/32/0/1669360384185-1-0-0.tsfile
> -rw-r--r-- 1 atmos root 0 Nov 25 15:34
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/data/sequence/root.sg1/38/0/1669361656927-1-0-0.tsfile
> -rw-r--r-- 1 atmos root 0 Nov 25 15:41
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/data/sequence/root.sg1/50/0/1669362077038-1-0-0.tsfile
> -rw-r--r-- 1 atmos root 0 Nov 25 14:34
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/data/sequence/root.sg1/6/0/1669358088441-1-0-0.tsfile
> {code}
> find $IOTDB_HOME/data/datanode/data -type f | xargs ls -hl
> {code}
> -rw-r--r-- 1 atmos root 54 Nov 25 14:30
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/system/users/root.profile
> -rw-r--r-- 1 atmos root 136 Nov 25 14:43
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-10/_0-0-1.wal
> -rw-r--r-- 1 atmos root 155 Nov 25 14:43
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-10/_0.checkpoint
> -rw-r--r-- 1 atmos root 68 Nov 25 14:59
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-19/_0-0-1.wal
> -rw-r--r-- 1 atmos root 155 Nov 25 14:59
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-19/_0.checkpoint
> -rw-r--r-- 1 atmos root 68 Nov 25 14:59
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-25/_0-0-1.wal
> -rw-r--r-- 1 atmos root 155 Nov 25 14:59
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-25/_0.checkpoint
> -rw-r--r-- 1 atmos root 68 Nov 25 15:13
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-32/_0-0-1.wal
> -rw-r--r-- 1 atmos root 155 Nov 25 15:13
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-32/_0.checkpoint
> -rw-r--r-- 1 atmos root 68 Nov 25 15:34
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-38/_0-0-1.wal
> -rw-r--r-- 1 atmos root 155 Nov 25 15:34
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-38/_0.checkpoint
> -rw-r--r-- 1 atmos root 68 Nov 25 15:41
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-50/_0-0-1.wal
> -rw-r--r-- 1 atmos root 155 Nov 25 15:41
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-50/_0.checkpoint
> -rw-r--r-- 1 atmos root 136 Nov 25 14:34
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-6/_0-0-1.wal
> -rw-r--r-- 1 atmos root 154 Nov 25 14:34
> /data/iotdb/apache-iotdb-0.14.0-SNAPSHOT-all-bin/data/datanode/wal/root.sg1-6/_0.checkpoint
> {code}
> 另外：
> 反复创建同一名称的aligned和nonAligned timeseries 并插入数据然后drop database root.**, 可能会导致
> root.sg1 在show regions时有成倍的dataregion。
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
