You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Marton Elek (Jira)" <ji...@apache.org> on 2020/02/17 13:05:00 UTC

[jira] [Assigned] (RATIS-816) Use peerId in error log / exception of GrpcServerProtocolClient

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

Marton Elek reassigned RATIS-816:
---------------------------------

    Assignee: Marton Elek

> Use peerId in error log / exception of GrpcServerProtocolClient
> ---------------------------------------------------------------
>
>                 Key: RATIS-816
>                 URL: https://issues.apache.org/jira/browse/RATIS-816
>             Project: Ratis
>          Issue Type: Improvement
>            Reporter: Marton Elek
>            Assignee: Marton Elek
>            Priority: Major
>
> GrpcServerProtocolClient is used to send out requestVote and appendLogEntry requests.
> I propose to persist raftPeerId in the constructor and use it in the error / exception message.
> This is not just getting more meaningful message (it's a nice to have) but in HDDS-3023 I am modifying the byte code to mock the leader->follower communication. It's way more easier to do if the required raftPeerId is available in the class.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)