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 02:43:00 UTC

[jira] [Commented] (IOTDB-5712) Concurrent bug in memory pool caused by identitySink

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

刘珍 commented on IOTDB-5712:
---------------------------

与IOTDB-5716同一个测试环境。

> Concurrent bug in memory pool caused by identitySink
> ----------------------------------------------------
>
>                 Key: IOTDB-5712
>                 URL: https://issues.apache.org/jira/browse/IOTDB-5712
>             Project: Apache IoTDB
>          Issue Type: Bug
>            Reporter: Alima777
>            Assignee: Alima777
>            Priority: Major
>              Labels: pull-request-available
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Alls sinkChannels of identitySink shares the planNodeId of identitySinkNode. Therefore, when the first child closes the sharedTsBlockQueue, it will try to clear the queryMemoryMap related about planNodeId. However, the second child can reserve, free or clear the queryMemoryMap of the same planNodeId concurrently.



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