[
https://issues.apache.org/jira/browse/RATIS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated RATIS-816:
------------------------------
Fix Version/s: 0.6.0
> 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
> Fix For: 0.6.0
>
> Attachments: RATIS-816.001.patch, RATIS-816.002.patch,
> RATIS-816.003.patch, RATIS-816.004.patch
>
>
> 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)
