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

Posted to notifications@iotdb.apache.org by "Yuan Tian (Jira)" <ji...@apache.org> on 2022/11/18 02:32:00 UTC

[jira] [Created] (IOTDB-4978) DeadLock caused by blocked operation in IntoOperator

Yuan Tian created IOTDB-4978:
--------------------------------

             Summary: DeadLock caused by blocked operation in IntoOperator
                 Key: IOTDB-4978
                 URL: https://issues.apache.org/jira/browse/IOTDB-4978
             Project: Apache IoTDB
          Issue Type: Bug
          Components: Core/Query
            Reporter: Yuan Tian
            Assignee: Minghui Liu


There are only fixed threads for query execution, so we shouldn't let blocked operation like rpc call in it. The following case may cause deadlock:

2c machines

2 clients concurrently execute `select into`, then IntoOperator will occupy the only two query execution threads to send write requests which are blocked operation. However, write operation will fetch schema which will only need query execution threads to do that. Bump, deadlock borns.



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