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

Posted to notifications@iotdb.apache.org by "Haonan Hou (Jira)" <ji...@apache.org> on 2022/04/26 15:07:00 UTC

[jira] [Assigned] (IOTDB-3016) Run flush when graceful stop IoTDB

     [ https://issues.apache.org/jira/browse/IOTDB-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Haonan Hou reassigned IOTDB-3016:
---------------------------------

    Assignee: Bo Zhang

> Run flush when graceful stop IoTDB 
> -----------------------------------
>
>                 Key: IOTDB-3016
>                 URL: https://issues.apache.org/jira/browse/IOTDB-3016
>             Project: Apache IoTDB
>          Issue Type: Improvement
>          Components: Core/Others
>            Reporter: Bo Zhang
>            Assignee: Bo Zhang
>            Priority: Major
>             Fix For: master branch
>
>
> When we test  1 IoTDB server who has many storagegroups and high TPS, we found below case:
> ==========================================================
> When we closed this IoTDB instance and then restarted it, the IoTDB spent more than 5 minutes before begining to provide service for clients.
> After analyzing,  we found that the reason is :
> 1) IoTDB server's shutdown cause much WAL logs were kept in Disk.  
> 2) When IoTDB restart, it will spend much time to recover from much WAL logs.
> ==============================================
> So we plan to add flush action before graceful closing IoTDB process.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)