[
https://issues.apache.org/jira/browse/IOTDB-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493112#comment-17493112
]
刘珍 commented on IOTDB-2528:
---------------------------
在1205pre2上复现出mlog崩溃的情况。
同样的用例在1205pre4执行，通过。
使用bm测试，配置文件见附件。
./benchmark.sh > 1.out &
sleep 30
/data/iotdb/1205_pre2/sbin/start-cli.sh -e "count timeseries"
kill -9 15635 // iotdb pid
./benchmark.sh > 2.out &
/data/iotdb/1205_pre2/sbin/start-cli.sh -e "count timeseries root.t2.*.*"
/data/iotdb/1205_pre2/sbin/start-cli.sh -e "count timeseries root.test.*.*"
sleep 600
/data/iotdb/1205_pre2/sbin/start-cli.sh -e "count timeseries root.t2.*.*"
/data/iotdb/1205_pre2/sbin/start-cli.sh -e "count timeseries root.test.*.*"
kill -9 18345
> MLog corruption and recovery bug after killing system
> -----------------------------------------------------
>
> Key: IOTDB-2528
> URL: https://issues.apache.org/jira/browse/IOTDB-2528
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Schema Manager
> Affects Versions: 0.13.0, 0.12.4
> Reporter: Yukun Zhou
> Assignee: Haiming Zhu
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.13.0, 0.12.5
>
> Attachments: image-2022-02-10-20-01-00-677.png,
> image-2022-02-11-11-38-50-593.png
>
>
> There're two problems.
> First, where creating timeseries via session, the usage of double quote in
> measurementId is not checked, which results in illegalPathException during
> revocery.
> Second, since mlog is not force sync at every metadata operation, some
> metadata may be lost after killing system during timeseries creation and
> recovery. Besides, the corrupted mlog will be used to recording new metadata
> operation, but the corrupted record will prevent mmanager from reading the
> following records, which also results in metadata lost.
> !image-2022-02-10-20-01-00-677.png!
>
> !image-2022-02-11-11-38-50-593.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
