You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2017/05/18 19:31:04 UTC

[jira] [Commented] (RATIS-86) Support server re-initialization

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

Jing Zhao commented on RATIS-86:
--------------------------------

Thanks for the patch, Nicholas! The patch looks good to me. Just two minor comments:
# Do you think we can rename ManagementProtocol to RaftGroupAdminProtocol?
# Semantically ReinitializeRequest may not be a subclass of SetConfigurationRequest. Later if we support multiple raft groups then these two requests may diverge: ReinitializeRequest will initialize/add a raft group, and SetConfigurationRequest will change the members of raft group.


> Support server re-initialization
> --------------------------------
>
>                 Key: RATIS-86
>                 URL: https://issues.apache.org/jira/browse/RATIS-86
>             Project: Ratis
>          Issue Type: New Feature
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>         Attachments: r86_20170511.patch, r86_20170512b.patch, r86_20170512.patch, r86_20170515.patch, r86_20170516.patch
>
>
> When a RaftServer is built, it creates a RaftServerImpl object and starts running a RaftServerRpc service.  The RaftServerImpl captures ServerState including RaftLog and RaftConfiguration.
> We want to support server re-initialization so that a server can support multiple raft clusters sequentially.  This is our first step to support multi-raft.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)