[IGNITE-16183] Raft heartbeat coalescing prototype

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: ignite-3
• Epic Link: AI3 Performance
• Assignee: Unassigned
• Reporter: Vyacheslav Koptilin
• Created: 21/Dec/21 16:52
• Updated: 08/Nov/24 06:32

Description

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/

Issue Links

• causes: IGNITE-17625 Investigate message coalescing techniques and an ability to add it to Ignite network
• is a child of: IGNITE-14832 Investigate remaining TODOs in org.apache.ignite.raft.jraft package
• relates to: IGNITE-23597 Idle Raft Replicator eats too much CPU