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

Posted to notifications@iotdb.apache.org by "yanze chen (Jira)" <ji...@apache.org> on 2023/03/23 07:31:00 UTC

[jira] [Commented] (IOTDB-5720) Release processor fail to release memory due to writer-preferred starvation

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

yanze chen commented on IOTDB-5720:
-----------------------------------

https://github.com/apache/iotdb/pull/9422

> Release processor fail to release memory due to writer-preferred starvation
> ---------------------------------------------------------------------------
>
>                 Key: IOTDB-5720
>                 URL: https://issues.apache.org/jira/browse/IOTDB-5720
>             Project: Apache IoTDB
>          Issue Type: Bug
>            Reporter: yanze chen
>            Assignee: yanze chen
>            Priority: Major
>         Attachments: image-2023-03-23-15-26-27-207.png
>
>
> !image-2023-03-23-15-26-27-207.png|width=488,height=155!
> [https://apache-iotdb.feishu.cn/docx/WwdAd6SYLofsAHxEJeRcDuWBnPh]
>  
> The current stampedLock uses a writer-preferred rule, which may lead to extreme cases where a waiting write lock request blocks the subsequent release thread from acquiring the read lock, resulting in memory not being released. To solve this problem, a high priority read lock request interface needs to be introduced.



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