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

Posted to notifications@iotdb.apache.org by "刘珍 (Jira)" <ji...@apache.org> on 2023/03/23 09:21:00 UTC

[jira] [Commented] (IOTDB-5665) Drop Database while writing

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

刘珍 commented on IOTDB-5665:
---------------------------

drop database root.** 会因为confignode重试而返回给客户端Msg: 508: Path [root.test.*] does not exist
这个问题需要解决，系统中是存在database的，返回这个报错信息不合适。

> Drop Database while writing
> ---------------------------
>
>                 Key: IOTDB-5665
>                 URL: https://issues.apache.org/jira/browse/IOTDB-5665
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: Yongzao Dan
>            Assignee: Yongzao Dan
>            Priority: Major
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> This is a special scenario. In this case, both the PartitionCache and SchemaCache are too busy to be released, for which will eventually lead to a failure of deleting Database. Thus, we should discuss the functional definition of this scenario.
>  
> For example, we can delete the database in force if the writeLock in PartitionCache should at least use the fair lock or have a higher priority.



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