You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Jialin Qiao (Jira)" <ji...@apache.org> on 2022/07/29 08:57:00 UTC
[jira] [Assigned] (IOTDB-3914) [MultiLeaderConsensus] Generate out-of-order data, follower nodes have direct write
[ https://issues.apache.org/jira/browse/IOTDB-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jialin Qiao reassigned IOTDB-3914:
----------------------------------
Assignee: Yongzao Dan (was: 张洪胤)
> [MultiLeaderConsensus] Generate out-of-order data, follower nodes have direct write
> -----------------------------------------------------------------------------------
>
> Key: IOTDB-3914
> URL: https://issues.apache.org/jira/browse/IOTDB-3914
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
> Affects Versions: 0.14.0-SNAPSHOT
> Reporter: 刘珍
> Assignee: Yongzao Dan
> Priority: Major
> Attachments: image-2022-07-21-11-34-23-458.png, image-2022-07-21-11-34-37-254.png, ip3_config.properties, ip4_config.properties, ip5_config.properties
>
>
> MultiLeaderConsensus,写入的数据有乱序(客户端写入的是顺序数据),3副本中的2个follower节点都有直接写入。
> 复现流程
> 1. 192.168.130.1/2/3/4/5
> 3副本3C5D
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.multileader.MultiLeaderConsensus
> schema_replication_factor=3
> data_replication_factor=3
> ConfigNode:
> MAX_HEAP_SIZE="4G"
> DataNode:
> MAX_HEAP_SIZE="16G"
> wal_buffer_size_in_byte=1048576
> max_waiting_time_when_insert_blocked=3600000
> query_timeout_threshold=36000000
> 2. benchmark在ip2
> /home/benchmark/bm_0620_7ec96c1
> 启动3个benchmark,配置文件见附件
> ip1
> !image-2022-07-21-11-34-23-458.png!
> 及对应的wal
> !image-2022-07-21-11-34-37-254.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)