You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2025/04/02 14:17:00 UTC

[jira] [Commented] (IGNITE-24788) Configurable coalescing for RAFT heartbeat

    [ https://issues.apache.org/jira/browse/IGNITE-24788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940377#comment-17940377 ] 

Vladislav Pyatkov commented on IGNITE-24788:
--------------------------------------------

Merged 756e68a61403af3c9b05f0a9de85a4cdea0c45d8

> Configurable coalescing for RAFT heartbeat
> ------------------------------------------
>
>                 Key: IGNITE-24788
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24788
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.1
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> h3. Motivation
> Some RAFT groups are not meant to store user data (CMG, Metastorage). These groups should have stronger latency guarantees than the table RAFT groups. But currently all groups coalesce their heartbeat messages into one (IGNITE-24788).
> h3. Definition of done
> The heartbeat coalescing has to be configurable for a specific RAFT group.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)