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

Posted to notifications@iotdb.apache.org by "zhenqqiang (Jira)" <ji...@apache.org> on 2022/07/22 11:55:00 UTC

[jira] [Created] (IOTDB-3933) In the hypermetro version, when IOTDB B is down, IOTDB A tries to write data to B, causing CPU and disk reads and writes.

zhenqqiang created IOTDB-3933:
---------------------------------

             Summary: In the hypermetro version, when IOTDB B is down, IOTDB A tries to write data to B, causing CPU and disk reads and writes. 
                 Key: IOTDB-3933
                 URL: https://issues.apache.org/jira/browse/IOTDB-3933
             Project: Apache IoTDB
          Issue Type: Bug
    Affects Versions: 0.13.0
            Reporter: zhenqqiang


In the hypermetro version, when IOTDB B is down, IOTDB A tries to write data to B, causing CPU and disk reads and writes. The CPU increases to 100%. This can be optimized as: when Iotdb B is down, one thread queries THE status of B. When B is normal, the thread continues to fetch data from the queue and read disks.



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