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

Posted to issues@ratis.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2019/06/27 13:39:00 UTC

[jira] [Commented] (RATIS-605) Add a RaftGroupMemberId class to encapsulate server identity in multi-raft

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

Tsz Wo Nicholas Sze commented on RATIS-605:
-------------------------------------------

r605_20190627.patch: adds RaftGroupMemberId.

> Add a RaftGroupMemberId class to encapsulate server identity in multi-raft
> --------------------------------------------------------------------------
>
>                 Key: RATIS-605
>                 URL: https://issues.apache.org/jira/browse/RATIS-605
>             Project: Ratis
>          Issue Type: Improvement
>          Components: server
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Major
>         Attachments: r605_20190627.patch
>
>
> In multi-raft, a server may belong to more than one groups so that the RaftPeerId is not enough to identity a particular group that the server belong to.



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