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

Posted to issues@kudu.apache.org by "Anirban Rahut (JIRA)" <ji...@apache.org> on 2019/01/16 19:47:00 UTC

[jira] [Created] (KUDU-2663) src/kudu/consensus/consensus.txt seems out of date

Anirban Rahut created KUDU-2663:
-----------------------------------

             Summary: 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
            Reporter: Anirban Rahut


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
(v7.6.3#76005)