[
https://issues.apache.org/jira/browse/KUDU-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bankim Bhavsar reassigned KUDU-2663:
------------------------------------
Assignee: Mahesh Reddy
> src/kudu/consensus/consensus.txt seems out of date
> --------------------------------------------------
>
> Key: KUDU-2663
> URL: https://issues.apache.org/jira/browse/KUDU-2663
> Project: Kudu
> Issue Type: Bug
> Components: documentation
> Affects Versions: 1.8.0
> Reporter: Anirban Rahut
> Assignee: Mahesh Reddy
> Priority: Minor
> Labels: newbie
>
> I am trying to build Kudu from source and also improve it more, and running
> into some understanding issues.
> Here is some of the documentation in consensus.txt
>
> RaftConfig membership changes:
> ------------------------------
> A two-phase joint consensus protocol is used for making cluster membership
> changes, including changing members of the config or the size of the
> majority. See RAFT section 6 and figure 11 for details.
>
> NOTE: membership changes are not yet implemented in Kudu.
>
> ----
> Is this still valid that consensus does not support membership changes?
> Can we update consensus.txt to reflect current reality?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
