[
https://issues.apache.org/jira/browse/IGNITE-16183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583578#comment-17583578
]
Alexey Scherbakov commented on IGNITE-16183:
--------------------------------------------
It seems coalescing is useful not only for RAFT messages, but for all cluster
communication. So, it makes a sense to implement it on a transport level.
> Raft heartbeat coalescing prototype
> -----------------------------------
>
> Key: IGNITE-16183
> URL: https://issues.apache.org/jira/browse/IGNITE-16183
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> Currently, the dedicated raft group is created for every partition. This
> approach leads to creating a huge number of raft groups which is expensive.
> In order to optimise a multi raft group architecture, our competitors uses
> some techniques, one technique is to merge several heartbeat from different
> raft groups from one node and send it as one. We need to prototype such
> approach and check it.
> Some different optimisations can be found here
> https://tikv.org/deep-dive/scalability/multi-raft/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
