[jira] [Resolved] (RATIS-1465) Use seperate channel for group heartbeat

["Tsz-wo Sze (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RATIS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz-wo Sze resolved RATIS-1465.
-------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

The pull request is now merged.  Thanks, [~Sammi]!

> Use seperate channel for group heartbeat
> ----------------------------------------
>
>                 Key: RATIS-1465
>                 URL: https://issues.apache.org/jira/browse/RATIS-1465
>             Project: Ratis
>          Issue Type: Improvement
>          Components: server
>            Reporter: Sammi Chen
>            Assignee: Sammi Chen
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: 561_review.patch, follower-hb-process-latency-with-patch.png, follower-hb-process-latency.png, leader-hb-receive-latency-1.png, leader-hb-receive-latency-with-patch.png
>
>          Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> In a heavy load read/write cluster,  frequent leader step down is observed because of lost the majority heartbeat. 
> The investigation shows that follower side heartbeat process is very quick, while the leader side heartbeat latency is high.  See the attached metrics diagram. 
> This task aims to use seperate grpc channel for heartbeat to reduce the latency introduced by the network queuing. 



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