[
https://issues.apache.org/jira/browse/IOTDB-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638467#comment-17638467
]
Jinrui Zhang commented on IOTDB-4507:
-------------------------------------
We gave more optimization and bug fix to MultiLeaderCosnensus, which would
enhance the stability of write using MultiLeader. See this PR
[https://github.com/apache/iotdb/pull/8025.]
The error "connect connect to node" is usually caused by the error/pressure of
server side. This fix decreased the pressure of server side and optimized the
memory usage of DataNode, which should take effect to this issue. Let's test it
again to see whether this issue will be reproduced or not
> [SystemResourceIssue] Insert failed can't connect to node TEndPoint
> --------------------------------------------------------------------
>
> Key: IOTDB-4507
> URL: https://issues.apache.org/jira/browse/IOTDB-4507
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
> Affects Versions: 0.14.0-SNAPSHOT
> Reporter: FengQingxin
> Assignee: Jinrui Zhang
> Priority: Minor
> Attachments: config.properties, confignode-env.sh, datanode-env.sh,
> image-2022-09-23-08-44-57-017.png, iotdb-confignode.properties,
> iotdb-datanode.properties, log.tar.gz
>
>
> Reproduce steps：
> # Setup a cluster with 3C3D({color:#de350b}MultiLeaderConsensus{color})
> # Using 3BMs to insert data(Loop=2000)
> # Setup a cluster with 3C3D({color:#de350b}MultiLeaderConsensus{color})
> # Using 3BMs to insert data(Loop=4000 or Loop=6000)
> BM ----- 》 IoTDB Node
> 172.20.70.7 ----- 》 172.20.70.22
> 172.20.70.8 ----- 》 172.20.70.23
> 172.20.70.9 ----- 》 172.20.70.24
> !image-2022-09-23-08-44-57-017.png|width=510,height=409!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
