You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "huxiangpeng (Jira)" <ji...@apache.org> on 2023/02/15 08:03:00 UTC
[jira] [Commented] (IOTDB-5112) Fixed IoTConsensus synchronization stuck under low load or during restart
[ https://issues.apache.org/jira/browse/IOTDB-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688885#comment-17688885 ]
huxiangpeng commented on IOTDB-5112:
------------------------------------
Please see details in [feishu cloud doc|https://apache-iotdb.feishu.cn/docx/TekkdtRvTo181UxI2x0c42iTnsN].
> Fixed IoTConsensus synchronization stuck under low load or during restart
> -------------------------------------------------------------------------
>
> Key: IOTDB-5112
> URL: https://issues.apache.org/jira/browse/IOTDB-5112
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
> Reporter: Chao Wang
> Assignee: huxiangpeng
> Priority: Major
> Labels: pull-request-available
>
> error log: waiting target request timeout. current index: 20, target index: -1.
> Because when requestCache.size()! = MAX_REQUEST_CACHE_SIZE, nextSyncIndex does not reassign a value, this will cause a 10s delay in IoTConsensus synchronization under low load or during restart
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)