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/07/05 07:49:00 UTC

[jira] [Updated] (RATIS-605) Change RaftServerImpl and proto to use RaftGroupMemberId

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

Tsz Wo Nicholas Sze updated RATIS-605:
--------------------------------------
    Summary: Change RaftServerImpl and proto to use RaftGroupMemberId  (was: Change RaftServerImpl and proto to use RaftGroupMemberId class to encapsulate server identity in multi-raft)

> Change RaftServerImpl and proto to use RaftGroupMemberId
> --------------------------------------------------------
>
>                 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, r605_20190628.patch, r605_20190628b.patch, r605_20190628c.patch, r605_20190629.patch, r605_20190629b.patch, r605_20190703.patch, r605_20190703b.patch, r605_20190703c.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)