You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "Haiming Zhu (Jira)" <ji...@apache.org> on 2022/12/28 11:10:00 UTC

[jira] [Commented] (IOTDB-5285) TimePartition may be error when restarting with different time partition configuration

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

Haiming Zhu commented on IOTDB-5285:
------------------------------------

The time partition id is calculated by the time partition interval and timestamp in the data, so time partition id in the memory is different from that on the disk when time partition interval is changed after restart.

!time partition calculation.png!

> TimePartition may be error when restarting with different time partition configuration
> --------------------------------------------------------------------------------------
>
>                 Key: IOTDB-5285
>                 URL: https://issues.apache.org/jira/browse/IOTDB-5285
>             Project: Apache IoTDB
>          Issue Type: Bug
>            Reporter: Jinrui Zhang
>            Assignee: Haiming Zhu
>            Priority: Major
>         Attachments: time partition calculation.png
>
>
> Reproduce steps:
>  # generate data files using time partition configuration A (eg. 1 week)
>  # backup data files
>  # stop system and change time partition configuration to B (eg. 1 day)
>  # restart system and see the time partition in memory
>  ##  we can check the time partition using Arthas, the cmd is such as `ognl "@org.apache.iotdb.db.engine.StorageEngine@getInstance().dataRegionMap.get(new org.apache.iotdb.commons.consensus.DataRegionId(6)).tsfileManager.unsequenceFiles"`



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