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

Posted to issues@ratis.apache.org by "Mukul Kumar Singh (JIRA)" <ji...@apache.org> on 2018/07/29 05:13:00 UTC

[jira] [Updated] (RATIS-286) Add information about raft peers and rpc deplay in ServerInformationReply

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

Mukul Kumar Singh updated RATIS-286:
------------------------------------
    Summary: Add information about raft peers and rpc deplay in ServerInformationReply  (was: Add information about ratft peers and rpc deplay in ServerInformationReply)

> Add information about raft peers and rpc deplay in ServerInformationReply
> -------------------------------------------------------------------------
>
>                 Key: RATIS-286
>                 URL: https://issues.apache.org/jira/browse/RATIS-286
>             Project: Ratis
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 0.3.0
>            Reporter: Mukul Kumar Singh
>            Assignee: Mukul Kumar Singh
>            Priority: Major
>             Fix For: 0.3.0
>
>         Attachments: RATIS-286.001.patch
>
>
> In order to detect slowness of a followere/leader node in a ratis ring. The delay in rpc communication between nodes should be tracked. This jira proposes to add new fields to ServerInformationReply to return this information.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)